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.


Friday
24 October, 2014


face

Hace un par de días que se lanzó Kubuntu 14.10 Utopic Unicorn y los que somos usuarios de este sistema operativo gnu/linux lo tenemos muy fácil dar el salto a esta nueva versión. En la siguiente entrada aprenderemos cómo actualizar Kubuntu 14.04 a 14.10 en apenas 4 pasos, que en Cómo actualizar Kubuntu 14.04 a [&hellip


face

In part of my research, I have been heavily involved with building portfolios of optimization algorithms. Optimization algorithms stay at the root of many computational tasks, from designing laser mirror systems to neural network training. We want to find a minimum (or maximum) of some mathematical function, and for some functions it’s easier than for others.

For very many fairly hairy functions, the best state-of-art optimization algorithm is based on genetic algorithms and it’s called CMA-ES. It also has a very nice Python implementation by its original author, Nikolaus Hansen.

CMA-ES is still not as good as it could be on some functions with many local optima, but its performance can be much improved by establishing a restart strategy that will repeatedly restart it with varying population size and parameters. The best performing restart strategy is BIPOP-CMA-ES and unfortunately, it had no Python implementation so far. I took care of that more than a month ago, but since it’s taking some time to get my modifications upstreamed, if anyone would find that useful,

here is a patch for CMA-1.1.02 adding BIPOP restart strategy


face

Avec la sortie d'openSUSE 13.2 en novembre, deux des projets d'openSUSE, les variantes en rolling release 'Tumbleweed' et 'Factory', vont fusionner pour n'en offrir qu'une seule sous le nom de Tumbleweed. Cette fusion se fait dans la logique du nouveau modèle de développement d'openSUSE.

Factory restera le nom du processus de développement grâce auquel les nouveautés sont intégrées tandis


face

Una noticia que era esperada en la comunidad de openSUSE: Tumbleweed y Factory se unirán.

fondo1

La noticia se hacía pública hoy, y es algo que desde hace tiempo se esperaba, cuando se anunció el modelo rolling release de Factory.

Con el lanzamiento de openSUSE 13.2 en noviembre, dos de los proyectos de openSUSE, que son Tumbleweed, y Factory se unirán y serán ofrecidas como un solo proyecto rolling release bajo el nombre de Tumbleweed.

Factory seguirá denominando a la rama de trabajo de openSUSE donde se desarrollan nuevas funcionalidades, y la rama de trabajo rolling release con software testeado se llamará Tumbleweed desde el próximo 4 de noviembre.

Al respecto, el presidente del consejo de openSUSE, Richard Brown ha comentado:

Con el lanzamiento de openSUSE 13.2 en noviembre, hemos creido que era una buena oportunidad para unir los dos proyectos rollinf release de openSUSE, así los usuarios de Tumbleweed se podrán beneficiar del proceso de desarrollo de Factory de los últimos años.

La combinación de comentarios y contribuciones de los usuarios de Tumbleweed y Factory debería ayudar impulsar a openSUSE hacia adelante, incluso de una manera más rápida, mientras ofrecemos a nuestros usuarios la último y aplicaciones mejores en una modelo rolling release estable.

Los detalles técnicos sobre esta noticia serán publicados alrededor del 4 de noviembre, para explicar que pasos son necesarios para migrar de una manera cómoda al modo combinado de tumbleweed rolling release.

Greg Kroah-Hartman desarrollador de Linux y creador de Tumbleweed ha comentado:

Los cambios del modelo de lanzamiento de Factory han cambiado de ser un desarrollo inestable a ser un tipo de rolling release parecido a lo que pensé cuando cree openSUSE Tumbleweed. Estoy muy contento de ver estos dos modelos de rolling release se unan bajo el nombre de Tumbleweed, estaré pendiente de ver cómo se desarrolla en el futuro.

Geeko+E17

Así que como podéis comprobar el modelo de desarrollo actual de Factory siendo rolling release pasará a ser Tumbleweed en detrimento de lo que hasta ahora venía siendo ese proyecto.

Y Factory seguirá siendo el sitio donde desarrollar nuevas tecnologías e ir trabajando en el modelo de desarrollo para futuras versiones.

A partir del lanzamiento de openSUSE tendremos más noticias, de las que por aquí estarás informado.

Puedes leer el anuncio oficial aqui:

Si necesitas más información importante y preguntas que tengas, echale un vistazo a este correo de Richrad Brown al respecto:

Al que puedes contribuir con tus dudas, etc…

Geeko_ascii

————————————————-



face


Σύμφωνα με τα τελευταία νέα, οι εκδόσεις openSUSE Tumbleweed και Factory θα γίνουν μία. Σαν Factory θα συνεχίσει να αναπτύσσεται η επερχόμενη έκδοση (όπως γινόταν παλιότερα). Για τις τεχνικές πληροφορίες πως θα γίνει αυτό, θα γραφτούν πολλά όσο πλησιάζει η 4 Νοεμβρίου, ημερομηνία κυκλοφορίας της 13.2.

Τελευταία, αναφέρθηκαν αφενός πολλές εγκαταστάσεις Factory σε υπολογιστές, αφετέρου σταθερότητα του Factory. Να θυμίσουμε ότι σαν Factory αναφέρεται η έκδοση Rolling (κυλιόμενη), όπου λαμβάνει ότι τελευταίο κυκλοφορεί από λογισμικό. Περνάει πρώτα από διπλό έλεγχο από το Factory-testing.

Το project Tumbleweed είχε ξεκινήσει από τον Greg Kroah-Hartman, και την εποχή εκείνη θεωρούνταν ως Rolling. Η αλήθεια είναι ότι ήταν ημι-rolling. Λάμβανε μόνο τις αναβαθμίσεις των τελευταίων σταθερών λογισμικών. Με κάθε νέα έκδοση της διανομής, λάμβανε όλα τα τρέχοντα-σταθερά πακέτα και συνέχιζε από εκείνο το σημείο την ενημέρωσή του (λάμβανε αρκετά πακέτα από τα τότε Factory).

Προσωπικά θεωρώ ότι δεν υπήρχε λόγος συντήρησης των δυο (προφανώς κάτι τέτοιο θα σκεφτήκανε και στην κοινότητα). Επίσης η ονομασία Factory (ως Rolling) μπέρδευε τον περισσότερο κόσμο που είχε συνδέσει την ονομασία Factory με δοκιμαστική έκδοση. Οπότε από θέμα "μάρκετινγκ", υπάρχει διαφορά.

Έτσι θα έχουμε:
openSUSE Tumbleweed την κυλιόμενη (rolling) διανομή
openSUSE Factory την προς ανάπτυξη έκδοση της διανομής (θα αποτελεί βάση για τις επόμενες εκδόσεις)

face

With the release of openSUSE 13.2 in November, two of openSUSE’s open-source projects, the ‘Tumbleweed’ and ‘Factory’ rolling releases will be merging, and offered as a single openSUSE rolling release under the name ‘Tumbleweed’

Factory will remain the name of the development process where openSUSE’s new developments are integrated, with the tested, user-ready rolling release assuming the name Tumbleweed from Nov. 4.

“With the release of openSUSE 13.2 due in November, we realised this was a perfect opportunity to merge our two openSUSE rolling-releases together so users of Tumbleweed can benefit from the developments to our Factory development process over the last few years,” said Richard Brown, Chairman of openSUSE board. “The combined feedback and contributions from our combined Tumbleweed and Factory users should help keep openSUSE rolling forward even faster, while offering our users the latest and greatest applications on a stable rolling release.”

Technical details for existing Factory and Tumbleweed users will be published closer to Nov. 4 to explain what steps need to be carried out to smoothly migrate to the new ‘combined’ Tumbleweed rolling release.

“The changes to the Factory release model have changed it from being an unstable development codebase into the type of rolling release I set out to create when starting openSUSE Tumbleweed,” said Greg Kroah-Hartman, Linux Kernel Developer and creator of openSUSE Tumbleweed. “I’m very happy to see these two rolling releases coming together under the name Tumbleweed, and am looking forward to watching how it develops in the future.”

Establishing Factory as the clear ‘development project’ for the ‘ready-to-use’ Tumbleweed rolling release clarifies Factory’s role as a development codebase for openSUSE software, alongside Tumbleweed as user-ready distribution with rolling, tested updates, Brown said.


face

While ago new version 3.19 of UnReal World RPG was released. It was very smooth release in my part. Everything was working as expected. Packages were build to several platforms that were planned. Those platforms were Ubuntu 10.04, 12.04, 14.04 and openSUSE 12.2,12.3,13.1 all there packages build from openSUSE 13.1 base distribution. Nobody found nothing to complain about binary packages before someone launched them on Arch distribution.

Good, Bad and Ugly CURL

Curl is nice library for transferring anything from anywhere that have some kind of protocol over internet. It’s been stable for ages and have nice programming interface. So we thought this is easy new dependency for URW. We should know better.

User installed Ubuntu deb package and tried to launch URW in Arch received error  that was:

/usr/lib/libcurl.so.4: version `CURL_OPENSSL_3' not found

Ok very nice and constructive error message. What to do? This in the dark side of Linux knowledge. If you search from web what this means you will notice there is plenty of packages that suffers from this. mostly they are proprietary like URW and build to work with Ubuntu and don’t work with Arch. It has something to do with openSSL and how old it is but that is far I debugged it.

ARGH ARCH!

So I installed Arch Virtualbox and started to research on this. So how to find it there ‘CURL_OPENSSL_3‘ in libcurl.so.4 or not. use ‘strings’ command (now you should say, “elementary dear Watson”, so you you don’t look stupid).

strings /usr/lib/libcurl.so.4 | grep CURL_OPENSSL_3

And no there is nothing with that name but

strings /usr/lib/libcurl.so.4 | grep CURL_OPENSSL_

Gives a shot. There is ‘CURL_OPENSSL_4‘ so what to do? You can’t do nothing if you don’t get very hazardous. You can sed ‘CURL_OPENSSL_4‘  to ‘CURL_OPENSSL_3‘ but there is no promises it will work and it’s not very convenient.

You can get Ubuntu deb, extract curl.so out of it and use LD_LIBRARY_PATH-variable (how to do that?  or use OpenSUSE version of URW that works out-of-the-box.

Nor of them is very elegant. Probably we’ll have to start building Arch package also because that is most elegant version of this.

 


face
很久沒有燒錄音樂CD了 ^^
之前燒錄的時候, 都會覺得不同的音樂曲目在切換的時候音量大小都不一樣.
所以要調整音量很麻煩.

所以今天在使用 K3B 的時候有稍微注意一下, 進階的選項
發現有 將音量等級同化 這個選項.
但是當你勾選的時候, 就會告訴你沒有安裝 normalize 套件而無法執行.



解決方式當然是透過 yast2 sw_single 或是 zypper 來安狀套件解決
:-)

搜尋一下關鍵字
# zypper  search  normalize
Loading repository data...
Reading installed packages...

S | Name                             | Summary                      | Type      
--+----------------------------------+------------------------------+-----------
  | normalize                        | An Audio File Volume Norma-> | package   
  | normalize                        | An Audio File Volume Norma-> | srcpackage
  | normalize-debuginfo              | Debug information for pack-> | package   
  | normalize-debugsource            | Debug sources for package -> | package   
  | rsyslog-module-mmnormalize       | Contains the mmnormalize s-> | package   
  | xmms2-plugin-normalize           | Normalize Support for xmms2  | package   
  | xmms2-plugin-normalize-debuginfo | Debug information for pack-> | package   


利用 zypper install 安裝套件

# zypper   install  normalize
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
  normalize 

1 new package to install.
Overall download size: 62.8 KiB. After the operation, additional 163.6 KiB will 
be used.
Continue? [y/n/? shows all options] (y): y 輸入 y 同意安裝
Retrieving package normalize-0.7.7-1.6.x86_64
                                           (1/1),  62.8 KiB (163.6 KiB unpacked)
Retrieving: normalize-0.7.7-1.6.x86_64.rpm ...................[done (9.9 KiB/s)]
(1/1) Installing: normalize-0.7.7-1.6 ....................................[done]

安裝完畢將K3b 重新啟動就可以了
:-)





Enjoy it ~

face


That's what I saw today after trying to update Notes:


Not cool, that didn't seem to work too well. This can happen with third-party apps. But what to do? Just like with upgrades, you can call in the help of the occ command line tool which comes with ownCloud. Ideally, run it as user of your apache, something like this:
sudo -u wwwrun ./occ
It will give you an overview of what occ can do for you, looking something like this:
ownCloud version 7.0.2

Usage:
[options] command [arguments]

Options:
--help -h Display this help message.
--quiet -q Do not output any message.
--verbose -v|vv|vvv Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug
--version -V Display this application version.
--ansi Force ANSI output.
--no-ansi Disable ANSI output.
--no-interaction -n Do not ask any interactive question.


And a lot more.
From there, you can start an upgrade with:
sudo -u wwwrun ./occ upgrade
which is nice when the ownCloud upgrade process doesn't work. This can happen because php has a time-out set and if the amount of work takes longer than that timeout - it won't finish. Which can happen for example on very big installations, or on very light hardware (raspberry pi!).
But that wasn't my problem - things just got stuck in maintenance mode. And that is one of the options in the list: turn maintenance mode on and off! So I just proceeded (on advice of Arthur here in the office) to turn that off:
sudo -u wwwrun ./occ maintenance:mode --off
Lo and behold, it solved the problem for me.
If it doesn't, there is the maintenance:repair option which might fix the problem for you!

Tip: log rotation

In other news, I discovered that my owncloud.log file (to be found in your data folder) was 5.9 gigabytes big. Yeah, 6318901632 bytes. ownCloud can keep that file in check, but you have to enable that by adding the following to your config.php:
'log_rotate_size' => '100 MiB'
Of course, other values work, too. You can find this and more in config.sample.php, be sure to go over that file to see what you can and perhaps should configure. I personally would welcome any effort to give that file a user interface, or make it easier to reach - even with a text editor built into the admin UI... Although perhaps a more subtle approach of picking what should be visible or not would be better. In any case - anybody up for that?

Tim Serong: Watching Grass Grow

08:07 UTCmember

face

For Hackweek 11 I thought it’d be fun to learn something about creating Android apps. The basic training is pretty straightforward, and the auto-completion (and auto-just-about-everything-else) in Android Studio is excellent. So having created a “hello world” app, and having learned something about activities and application lifecycle, I figured it was time to create something else. Something fun, but something I could reasonably complete in a few days. Given that Android devices are essentially just high res handheld screens with a bit of phone hardware tacked on, it seemed a crime not to write an app that draws something pretty.

openSUSE wallpaperThe openSUSE desktop wallpaper, with its happy little Geeko sitting on a vine, combined with all the green growing stuff outside my house (it’s spring here) made me wonder if I couldn’t grow a little vine jungle on my phone, with many happy Geekos inhabiting it.

Android has OpenGL ES, so thinking that might be the way to go I went through the relevant lesson, and was surprised to see nothing on the screen where there should have been a triangle. Turns out the view is wrong in the sample code. I also realised I’d probably have to be generating triangle strips from curvy lines, then animating them, and the brain cells I have that were once devoted to this sort of graphical trickery are so covered in rust that I decided I’d probably be better off fiddling around with beziers on a canvas.

So, I created an app with a SurfaceView and a rendering thread which draws one vine after another, up from the bottom of the screen. Depending on Math.random() it extends a branch out to one side, or the other, or both, and might draw a Geeko sitting on the bottom most branch. Originally the thread lifecycle was tied to the Activity (started in onResume(), killed in onPause()), but this causes problems when you blank the screen while the app is running. So I simplified the implementation by tying the thread lifecycle to Surface create/destroy, at the probable expense of continuing to chew battery if you blank the screen while the app is active.

Then I realised that it would make much more sense to implement this as live wallpaper, rather than as a separate app, because then I’d see it running any time I used my phone. Turns out this simplified the implementation further. Goodbye annoying thread logic and lifecycle problems (although I did keep the previous source just in case). Here’s a screenshot:

Geeko Live Wallpaper

The final source is on github, and I’ve put up a release build APK too in case anyone would like to try it out – assuming of course that you trust me not to have built a malicious binary, trust github to host it, and trust SSL to deliver it safely ;-)

Enjoy!


Thursday
23 October, 2014


face

Ya tenemos entre nosotros el lanzamiento de Kubuntu 14.10 “Utopic Unicorn”, la nueva versión de la distribución que nos ofrece, por primera vez, la posibilidad de tener en nuestro escritorio Linux Plasma 5. Veamos sus novedades a grandes rasgos. Kubuntu 14.10 Utopic Unicorn La evolución de la distribución KDE de la familia Ubuntu, Kubuntu, ha [&hellip


face

Since the introduction of P-States in the Intel SandyBridge and newer processors and the introduction of the P-States driver in the kernel since 3.9 there have been some changes to the power management on systems in regards to userspace tools. It has moved from cpufreq to cpupower and you may have written a script in times past to help set the right power management governor for your system. On a system with P-States you find that using cpupower has no effect on the performance whatsoever when you change the governor with cpupower. In order to get high performance out of your system with P-States you will need to look at some parameters into sysfs and change them using the userspace tool cpupower. Lets have a look at what there is for P-States.

Change your directory to /sys/devices/system/cpu/intel_pstate

system:/sys/devices/system/cpu/intel_pstate # l
total 0
drwxr-xr-x  2 root root    0 Oct 21 18:45 ./
drwxr-xr-x 14 root root    0 Oct 21 18:45 ../
-rw-r--r--  1 root root 4096 Oct 21 18:45 max_perf_pct
-rw-r--r--  1 root root 4096 Oct 21 18:45 min_perf_pct
-rw-r--r--  1 root root 4096 Oct 21 18:45 no_turbo
We have the max_perf_pct and the min_perf_pct and if we cat these files we can see their values.
# cat max_perf_pct
100
# cat min_perf_pct
32
This is the default for a powersave governor which you can gather from running the following command.
# cpupower frequency-info
  analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 1.20 GHz - 3.70 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 1.20 GHz and 3.70 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 3.53 GHz (asserted by call to hardware).
  boost state support:
    Supported: yes
    Active: yes
    3500 MHz max turbo 4 active cores
    3500 MHz max turbo 3 active cores
    3600 MHz max turbo 2 active cores
    3700 MHz max turbo 1 active cores
Notice the driver is intel_pstate and the current policy is set to powersave

We want the performance governor. So we will need to change our governor to performance. Execute the following.
# cpupower frequency-set -g performance

# cpupower frequency-info
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 1.20 GHz - 3.70 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 1.20 GHz and 3.70 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.83 GHz (asserted by call to hardware).
  boost state support:
    Supported: yes
    Active: yes
    3500 MHz max turbo 4 active cores
    3500 MHz max turbo 3 active cores
    3600 MHz max


face

One of the things that has always been a bit of a struggle in Firefox for Android is getting reliable video decoding for H264. For a couple of years, we've been shipping an implementation that went through great heroics in order to use libstagefright directly. While it does work fine in many cases, we consistently get reports of videos not playing, not displayed correctly, or just crashing.

In Android 4.1, Google added the MediaCodec class to the SDK. This provides a blessed interface to the underlying libstagefright API, so presumably it will be far more reliable. This summer, my intern Martin McDonough worked on adding a decoding backend in Firefox for Android that uses this class. I expected him to be able to get something that sort of worked by the end of the internship, but he totally shocked me by having video on the screen inside of two weeks. This included some time spent modifying our JNI bindings generator to work against the Android SDK. You can view Martin's intern presentation on Air Mozilla.

While the API for MediaCodec seems relatively straightforward, there are several details you need to get right or the whole thing falls apart. Martin constantly ran into problems where it would throw IllegalStateException for seemingly no valid reason. There was no error message or other explanation in the exception. This made development pretty frustrating, but he fought through it. It looks like Google has improved both the documentation and the error handling in the API as of Lollipop, so that's good to see.

As Martin wrapped up his internship he was working on handling the video frames as output by the decoder. Ideally you would get some kind of sane YUV variation, but this often is not the case. Qualcomm devices frequently output in their own proprietary format, OMX_QCOM_COLOR_FormatYUV420PackedSemiPlanar64x32Tile2m8ka. You'll notice this doesn't even appear in the list of possibilities according to MediaCodecInfo.CodecCapabilities. It does, however, appear in the OMX headers, along with a handful of other proprietary formats. Great, so Android has this mostly-nice class to decode video, but you can't do anything with the output? Yeah. Kinda. It turns out we actually have code to handle this format for B2G, because we run on QC hardware there, so this specific case had a possible solution. But maybe there is a better way?

I know from my work on supporting Flash on Android that we use a SurfaceTexture there to render video layers from the plugin. It worked really well most of the time. We can use that with MediaCodec too. With this output path we don't ever see the raw data; it goes straight into the Surface attached to the SurfaceTexture. You can then composite it with OpenGL and the crazy format conversions are done by the GPU. Pretty nice! I think handling all the different YUV conversions would've been a huge source of pain, so I was happy to eliminate that entire


face

For years when I needed to search for something in 'vim', I would use the '/' command and type the search key. Usually this would be inefficient, because I would be typing the name of a function that was right there on the screen (sometimes I would use the mouse to copy-and-paste to save a few keystrokes, taxing my brain with yet another keyboard/mouse context switch and exacerbating my "mouse finger" syndrome). Imagine my surprise to learn that Vim has a '*' command to search for whatever word happens to be under the cursor! And then there are the 'n' and 'N' commands which search forwards and backwards, respectively, for the last search key.
Read more »


face

Hace unos días anunciamos que se había lanzado la primera actualización del  escritorio Plasma 5, el escritorio de linux más avanzado de la Comunidad KDE.  Hoy nos toca seguir hablando de las novedades qué nos ofrece,concretamente de las mejoras de los elementos del escritorio Plasma 5.1 El nuevo Plasma 5.1 El  15 de octubre fue [&hellip


face

openSUSE 13.2 comes with the latest and greatest that the GNOME desktop has to offer — GNOME 3.14. At the time of the release 13.2 offers GNOME 3.14.1, which improves upon the user-experience of GNOME 3.10, that came with openSUSE 13.1, several notches, featuring notably a much improved gnome-shell with pretty-but-subtle animations and multi-touch gestures for the first time. The core applications have all seen remarkable activity during the development of 3.14 (and earlier, 3.12), focused on exciting features but also to make the desktop experience more unified and consistent.

Activities overview

Video player

Evince, Notes, Font viewer

 

 

GNOME Shell

Calculator in the GNOME shell search

Calculator in the GNOME shell search

At the heart of the GNOME experience is the much improved GNOME Shell, handling such trifle as launching applications, switching between windows and workspaces with the grace of a ballet dancer. Gnome-shell, available at version 3.14.1 with openSUSE 13.2, has picked up the ability to respond to multi-touch gestures, including on touchscreens, to open the Activities overview, applications overview and message tray, and to switch between windows and workspaces. In addition, this latest version of the shell features a host of pretty-but-subtle animations that make working inside GNOME a real pleasure.

Typing in a search term in the gnome-shell’s activities overview now gives results for matching files, documents, notes, contacts, photos… and even features inline calculations (just type in 22/7 and see for yourself)!

The applications overview now lists “Sundry” and “Utility” applications in app-folders making the full list of applications less crowded and easier to navigate. In an openSUSE-special touch, the YaST modules are all classed into an app-folder of its own, making it straightforward to launch any YaST module straight from the shell.

Header-bars aka Client side window decorations

The support for header-bars, that nifty combination of window-header and toolbar in one screen real-estate saving gem, which started with 3.10 (so you should have seen a glimpse of this in openSUSE 13.1 already) has proliferated into all major applications. Core applications such as text-editor GEdit, Notes, eps/pdf viewer Evince, Music, Documents all benefit from this development. In addition header-bars have also picked up touchscreen support, so where one could not previously move windows with header-bars around by touch, this is now possible.

Is that a brand new video player?

Video player showing Apple Movie Trailers straight from the web

Video player showing Apple Movie Trailers straight from the web

No, it is still totem, for long GNOME’s default media player in openSUSE. Except now, in it’s 3.14 incarnation it has been completely revamped, now showing a list of videos in your home directory when launched and allowing you to switch to a list of online video channels at the touch of a button. The playback controls are now presented as a floating toolbar that automatically hides when you don’t need it, allowing the currently playing video


Wednesday
22 October, 2014


face

Moto 360 image

I must admit, I'm actually really happy with the Moto360. After reading a load of reviews and speaking to people that already had the device, I was fully prepared for a subpar experience. Maybe that's the beauty of not being a bleeding edge early adopter :-)

The woes that were extolled were many, and the only good thing people had to say were about the stunning good looks; battery life was woeful, not even lasting a day; performance was hit and miss; connectivity to phone was spotty; the list goes on, one almost wonders why on earth I would still want one. As it happens, both Google and Motorola have been fairly quick with updates to the device. Android Wear is still exceptionally young, having only been released at Google I/O this summer, but has already had at least two significant updates.

I've not had any connectivity issues between my Moto360 and my Nexus5, not once has my watch been unable to either connect to the internet or drop the connection. People complained that the vibration for notification was too weak. Seriously?! If it was any stronger my arm would shake as if I was suffering from some serious withdrawal symptoms. I genuinely find the vibration just right, strong enough to be certain it was a genuine notificationa and not a phantom notification as a result of my stomach rumbling because I craved something to eat. I'll be honest here, and those that know me won't be surprised at all by this statement, I'm not the most artistically observant person. Meaning I don't notice small variences in colour hues for icons and glyphs, I don't notice tiny pixelation, I don't notice things like Issue 41827, that is unless someone points it out to me and I look really hard. I may just see it then after a while, the Sad Santa thing took me quite a while to notice the difference.

After a full day of slightly above average usage (I ended up demoing it to my wife for a wee bit), I was left with 57% battery remaining - and that was before the latest update that purportedly improves battery life by upto 15%. Not bad considering many said it barely lasted half a day. I have managed to find one case where I was able to deplete the battery rather rapidly though, it is by no means disasterous as I was fully expecting battery to be impacted. That case was going for a 10km run using Endomondo, with active heart monitoring enabled. After an hour of exercise I had used 40% of my battery, as the screen was permanently on alongside the heart rate monitor taking a reading very regularily. Thankfully the watch charges pretty rapidly and within an hour I was back to a full battery. I love the fact that the Moto360 uses QI charging, which means I don't have to have the specific watch dock to


Frank Karlitschek: Ohio Linux Fest

21:52 UTCmember

face

This Friday the Ohio Linux Fest kicks off in downtown Columbus and I’ll be there! It is my first Linux Fest in the US so I greatly look forward to being introduced in this grand tradition. Of course, I’ll be talking about ownCloud on Saturday the 25, from 13:00 to 14:00 room D142-143.

The title of the talk is “crushing data silos with ownCloud”: helping people liberate their data from the centralized services they have stored it on. I don’t think that a world where most of the personal data of the world is stored on servers of a hand full companies is a good one. ownCloud is, right now, the best way of getting out of that world!
The talk will also cover a few interesting new ideas that we want to do in ownCloud to build a fully federated and distributed solution in the future.

It would be awesome to do a small ownCloud and/or KDE meetup there.

If you’re going to be there – let me know! Find me on twitter and lots of other social services!


face

Apple released Apple Pay yesterday with the iOS 8.1 update.  Randy and I went out at lunch to try it out and compare it to Google Wallet on his OnePlus One Android Phone.  We visited three locations: Maverik, McDonald's, and Macey's Grocery.  Both phones were able to make payments without any network connection however the Airplane mode on the OnePlus One also shut off the NFC radio.  The iPhone 6+ was able to pay even in Airplane mode.

Here are the steps to pay on the two phones:


Apple Pay
NFC Payments
  • Place the iPhone up to the payment terminal
  • Use Touch ID to authorize
  • Done
Google Wallet
  • Unlock your phone
  • Place your Phone up to the payment terminal
  • Enter your 4 digit Google Wallet PIN
  • Done

The steps above look about the same but what isn't mentioned there is it took a while to figure out how to make Google Wallet work.  If I were to write the steps it took the very first time we tried Google Wallet they would look like this:

Google Wallet (the first time)
  • Place the Phone up to the payment terminal
  • Wake the phone up and then try again
  • Unlock the phone and try again
  • Wave it around for a little bit hoping the people behind are not getting too upset
  • After a few seconds, finally enter your PIN in Google Wallet to unlock it
  • When no network is available, get a confusing message that sounds like the payment didn't work when in reality it did.  It was trying to tell you it cannot show the details yet because you are not connected, but it sounds more like the payment failed.
What's the point?

You may ask why even bother with the stuff?  Why is this easier than just using my credit card?  Last week I was mailed new credit cards.  I didn't ask for them but they were issued along with a letter about how Home Depot was compromised and these cards were sent to protect me.  Had I been using Apple Pay or Google Wallet every time I went to Home Depot, it wouldn't have mattered.

When you set up a credit card in Apple Pay a unique card number is generated that will only work with that iPhone, and only with your finger print.  When you shop at a store, the only number they get is the one generated for your phone.  To use that number someone would have to have your phone and your finger print.  When Home Depot or Target are compromised in the future, no useful information will exist on their insecure systems.

Look for the NFC Payments logo (above) and it's likely that you'll be able to pay using Apple Pay or Google Wallet.

-- Just a quick followup...  We went to lunch today at JCW's.  They had the NFC Payments symbol.  I was able to pay with Apple Pay.  Randy tried with Google Wallet and it wouldn't work.

face

What a conference!!! openSUSE Asia Summit was unforgettable. The whole event had an amazing feel to it, and I had a rocking time in Beijing. openSUSE really has one of the best and most helpful communities, and the people are amazing. I had the pleasure of interacting with the active organization community. You guys absolutely rock!!!

Here are some of my experiences, and things I learned at the conference:

A little history:
The beginnings of the summit go back a year to Thessaloniki, where the idea of the Asia Summit was first mooted. Due to time constraints and clashes with openSUSE Summit in the US called for the event to be shifted to 2014. I had interacted with Sunny and Max in Thessaloniki and loved the idea of having an openSUSE event in Asia. At oSC14 in Dubrovnik, it was more or less confirmed that the summit would take place.

The Organization Team:
I joined the organization team a little late. The others had already done a lot of the hard work. I helped around a little with the invite letter and the promotion of the logo contest, and trying to find people to help around with the artwork. The opening session, where we welcomed the attendees in our native languages was cool. Also, Sunny’s speech in the beginning, which took us through the past one year was memorable, and I still remember each and every word of it.

I would take this opportunity to thank the openSUSE.Asia Summit
organization team. Today, now the openSUSE.Asia summit has started,
I’m reminded of the journey we took to get here.
I can not forget our weekly meetings, which often lasted to midnight.
I can’t forget 137 cards in trello for the preparation tracking.
And I can’t forget hundreds of emails about the Summit in our mail
boxes.

When we were on the way to reach this summit, we encouraged and
supported each other. Even though we were tired, we never gave up,
because we did believe we would finally be here. It is my honor being
a member of such a great team!

There are 17 people in the organization team, I won’t list everyone’s
name because we are a team, and we couldn’t have make any success
without each of us.

-Sunny

The organization committee did a fantastic job with the event and everything was planned to perfection. I would love to work with you all to host openSUSE Asia Summit next time as well (hopefully in India ;) )

New things:
I absolutely loved the concept of ‘Chops’ where the workshop speakers would put a lovely ‘Geeko’ stamp on the brochure for the participants for the performance in the workshop. More than judging the performance, it gave us a good chance to interact with the attendees and have a lot of fun in the process. The gifts for the speakers and for the chops were great and well thought out. Personally, working with


Tuesday
21 October, 2014


face

I read an article today about how expensive the new iPhone 6 will be if you buy it off contract.  I admit, it's a lot of money but it's actually less money than what you'll pay if you buy it with a contract.

I recently switched back to AT&T from Verizon because they introduced a new plan called the Mobile Share Value plan that offers non-subsidized pricing if you own your phone.  There are two rates for each line on this plan. If you own your phone the rate is $15/month for the line.  If you buy a "contract price" phone that rate is $40/month for the line and you have a 2 year contract.


In case you didn't get that, they will charge you and extra $25/month for 2 years to pay for the rest of that phone.  Over 24 months that ends up being $600.
With that, here are the actual iPhone 6 Plus costs:

Contract Prices:
iPhone 6 Plus 16GB: $899
iPhone 6 Plus 64GB: $999
iPhone 6 Plus 128GB: $1099

Non-Contract Prices:
iPhone 6 Plus 16GB: $749
iPhone 6 Plus 64GB: $849
iPhone 6 Plus 128GB: $949 

The other thing to consider is with non-contract plans you don't have a 2 year contract.  I know that seems obvious but let me just say it once again... you don't have a 2 year contract.  You are free to terminate your service any time you want with no cancellation fees.


face

The biggest part of this HackWeek will be spent on Weblate. The major task is to complete new UI for it. There have been already some blog posts about that here, so regular readers of my blog already know it is using Twitter Bootstrap.

Today it has reached point where I think it's good enough for wider testing and I've deployed it at Hosted Weblate (see Weblate website for conditions for getting hosting there).

I expect there will be some rough edges, so don't hesitate to report any issues, so that I can quickly fix them.

Filed under: English phpMyAdmin SUSE Weblate | 0 comments | Flattr this!


face

hack weekHi everyone, I’m Doug! This is the beginning of my third week at openSUSE contributing to marketing and communications. It is great to be of the community. Everything here is new, and during my first week, I kept hearing people here talk about Hack Week.

Several thoughts of what Hack Week could be crossed my mind.

Having worked in government for several years, I associated hacking with bad people and bad intentions, which is why I thought I should visit the website and see what the hype was all about.

The ideas running through my head were way off.

I quickly learned Hack Week is about creating projects, being innovative and providing solutions for users, developers and industry. In other words, its an event openSUSE endorses to inspire people’s creativity and let them do something fun.

Most Popular Projects

One of the projects I saw on the website called “Using zypper to “upgrade” CentOS/RHEL to openSUSE/SLES” summed up the idea about Hack Week. This project is designed to take our package management tools and convert other Linux distributions to an openSUSE system.

Another project, lead by Vice President of Engineering for SUSE, Ralf Flaxa, that captured hackers’ attention was the SUSE Music(ian) Space project, which is about sharing knowledge on how to get music equipment to with with openSUSE.

The project I joined for Hack Week is the redesign of the openSUSE landing page. After the first day, the group has agreed on a page design and we are at the phase of creating prototype, which we plan to propose to the community for comments and feedback.

Hack Week is a great event and I’m excited to participate. Without hacking, innovation would stagnant, creativity would diminish. Happy Hacking!

 


Victorhck: Charlas de un #findenegro

09:56 UTCmember

face

#findenegro es una iniciativa promovida por la web elbinario.net donde diferentes hackers dieron charlas sobre temas diferentes.

¿Estás interesado en redes libres? ¿en una introducción al uso de Nmap? ¿sobre criptomonedas como ecoin? ¿y otros temas? entonces sigue leyendo… y escuchando!

Desde hace unos meses me topé con la web elbinario.net un espacio en la red que de principio ya me pareció distinto… Una web con sitio para leer y conocer temas distintos que no son los habituales en la blogosfera, ¿suena interesante, verdad?

extremistaLos administradores del sitio hablan de software libre y hacktivismo con convencimiento y conocimiento de causa, ya que se nota que dominan las materias que exponen en su web y además lo hacen de manera interesante, lo que es un gusto para la neurona!

Ya han realizado varias propuestas on-line para su comunidad de seguidores, y la última ha sido este pasado fin de semana (del 17 al 19 de octubre de 2014) con la celebración de lo que llamaron #findenegro.

Consistía en una serie de charlas repartidas en esos días con diferentes ponentes y que trataban temas muy diversos. Desde ecoins hasta la resolución de conflictos en comunidades hackers.

Las charlas de desarrollaron en audio en un servidor Mumble que montaron a tal efecto. En el que se podía interactuar con el ponente preguntando, compartiendo, etc. Esas charlas han sido grabadas y están disponibles para volver a escucharlas.

Yo tenía especial interés en escuchar las que Laura Arjona iba a dar sobre la red pump.io y otra sobre redes libres. No defraudó, fueron entretenidas (bueno, eso si eres un geek! ;) ) y Laura las expuso con buen hacer, lo que además hizo que fueran muy instructivas.

Pero además de estas también iba con la mente abierta a escuchar sobre otros muchos temas, que a priori no eran mucho de mi agrado. Y fue una gran sorpresa escuchar sobre ecoins, o sobre la resolución de conflictos, por poner un par de ejemplos.

Os animo a darle al play y descubrir sobre loss temas que más os puedan interesar. Podéis también descargaros los audios. (entre paréntesis adjunto mi puntuación de 0 a 5 es simplemente mi opinión personal)

Charlas del viernes 17-10-2014

  • [SSHD] charla sobre la forma de securizar un servidor SSH. (0)
  • [SQLMAP] Nociones para manejar SQLMap. (3)
  • [PeerTV] Aprender inglés montando tu propia TV P2P. (3)

Más información en: http://elbinario.net/2014/10/20/podcasts-charlas-findenegro-2014-viernes/

Charlas del sábado 18-10-2014

  • [AmayaOS] charla sobre el sistema operativo AmayaOS. (4)
  • [Pump] La red social libre. (5)
  • [Homeservertor] Montar un servidor casero anónimo con tor. (2)
  • [UFONet] Ataques DDoS utilizando vectores de webs de terceros. (2)

Más información en: http://elbinario.net/2014/10/20/podcasts-charlas-findenegro-2014-sabado/

Charlas del domingo 19-10-2014

  • [Nmap] Introducción a nmap. Escáner de puertos. (4)
  • [RedesLibres] El largo camino hacia las redes libres

face

Здравствуйте читатели, запах елок и ускорение темпа жизни возвещает нам о наступлении 2011 года И я спешу выложить все, что у меня накопилось в черновиках И расскажу я вам сегодня о том, как очень быстро, за несколько минут поднять VPN сервер. В принципе, ничего сложного нет, но следуя стилю всех постов в этом блоге, я [...]


face

Здравствуйте, сегодня расскажу вам о dnsmasq. Сам я познакомился с этой утилитой не так давно. Это очень легкий и простой в настройке DHCP, DNS и TFTP сервер(!). Если вам нужно очень быстро настроить офисный шлюз с нуля, без создания дополнительных внутренних зон, то dnsmasq станет идеальным вариантом. Dnsmasq имеет следующие возможности: - встроенный DNS сервер [...]


face

Сегодня хочу показать как сделать простейший роутер из компьютера с ОС openSUSE в течении нескольких минут. Сделать это сможет каждый, кто хоть немного знаком с консолью и понимает для чего нужны IP адреса . На моей машине внутренним интерфейсом является eth0(192.168.1.1), а внешним eth1. Начнем по порядку: I) Настройка сервера DNS: Устанавливаем: user@opensuse:~> sudo zypper [...]


face

Здравствуйте читатели, к сожалению, никак не хватает у меня времени сделать еще 2 статьи про быструю настройку NAT и прозрачное проксирование в openSUSE с помощью SQUID. Но надеюсь через 2 недели у меня появиться окошко и я, все-таки, реализую свои планы. А теперь о позитивном, недавно вернулся с конференции HighLoad ++. Узнал очень много нового [...]


face

Привет! Сегодня расскажу вам как быстро поднять файловый сервер в сети, весь процесс настройки не займет и 20 минут(разумеется, если у вас хорошая скорость интернета ) Поехали: 1) Устанавливаем Samba: user@linux-m71t:~> zypper install samba 2) Смотрим конфиг: Хочу рассказать здесь обо всех опциях, которые могут понадобится. По умолчанию в секции global следующие опции: user@linux-m71t:~> cat [...]


face

Здравствуйте, сегодня хочу рассказать, о том, как установить и настроить VirtualBox на сервере, с которым работа ведется только по SSH. Это очень удобно, если где-то у вас имеется мощный сервер, а хочется экспериментов, ставим VirtualBox, поднимаем RDP/VNC в системе, в зависимости от предпочтений и пользуемся Указанная последовательность настройки VirtualBox будет работать в любом линукс дистрибутиве. [...]

Older blog entries ->