1 Bilhão de raposas! Parabéns Firefox!

E disseram que não seria possível! AH!


Posted in Uncategorized | 1 Comment

Padoca agora serve asinhas de frango…

É isso aí, o padoca está no twitter (vejam aba do lado direito), através do mesmo poderão seguir os últimos softwares lançados no repo padoca, links de interesse e outras novidades que nem sempre merecem um artigo completo no blog, mas nem por isso deixam de ser interessantes.

Enjoy and keep tweeting!

Posted in Uncategorized | 1 Comment

Como consertar o strigi (desktop search) no kde 4.2 e 4.3

O KDE 4.x traz um desktop search do mesmo nivel do beagle e tracker no gnome, ou desktop search no macosx/windows, chamado strigi, que faz parte da desktop semântica, tecnologia que promete.

No entanto, devido a um erro de pacotes, o strigi vem “quebrado” por padrão.
Então, se você for em System Settings -> Advanced -> Desktop Search, e quando for ativar o botão Enable Strigi Desktop File Indexer, na tab Basic Settings, o strigi morrer com a mensagem “strigi service failed to initialize…”, faça o seguinte:

  • rode o comando: sudo ldd /usr/lib/soprano/libsoprano_sesame2backend.so

Isso deve mostrar algo como:

        linux-gate.so.1 =>  (0xb7f0e000)                                  
        libsoprano.so.4 => /usr/lib/libsoprano.so.4 (0xb7ded000)          
        libjvm.so => not found                                            
        libQtCore.so.4 => /usr/lib/libQtCore.so.4 (0xb7bb4000)            
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7ac5000)            
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7ab6000)                  
        libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7953000)            
        libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb793a000)
        libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7913000)            
        libz.so.1 => /lib/libz.so.1 (0xb78fd000)                          
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb78f7000)  
        librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb78ee000)          
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7836000)        
        libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7832000)          
        /lib/ld-linux.so.2 (0xb7f0f000)                                   
        libpcre.so.3 => /lib/libpcre.so.3 (0xb77ff000)

repare que a libjvm.so não está sendo encontrada.

Solução: rode:

  • sudo apt-get install sun-java6-bin
  • ln -s /usr/lib/jvm/java-6-openjdk/jre/lib/i386/server/libjvm.so /usr/lib/libjvm.so

reinicie o nepomuk (a maneira mais fácil é relogar no kde) e ative o serviço strigi, agora vai funcionar 🙂


Posted in Uncategorized | 4 Comments

The new kits on the block – Linux webkit based browsers review.

Since the original fork from KHTML, a lot of water as passed under the bridge of webkit development, to the point that as of today, webkit based browsers thrive all over linux land.

The padoca team decided to do some light testing and benchmark, and to check out what exactly is going on with webkit in the land of the penguin. So, without further ado…

Lets start by learning what exactly is webkit, courtesy of wikipedia 🙂

WebKit is an application framework that provides a foundation upon which to build a web browser. WebKit was originally derived by Apple Inc. from the Konqueror browser’s KHTML software library for use as the engine of Mac OS X’s Safari web browser and has now been further developed by individuals from the KDE project, Apple, Nokia, Google, Torch Mobile and others.[1] It has been ported to a number of different platforms and is now used as the rendering engine within a number of different pieces of software. WebKit is open source; its WebCore and JavascriptCore components are available under the GNU Lesser General Public License, and WebKit as a whole is available with a BSD-style license.[2]

So, that is that 😀 Webkit is a browser engine, like gecko is the browser engine for mozilla/firefox and friends.

Now, for something completely similar, who are there guys (browsers) anyway?

First and foremost, the grandfather of the webkit itself, the great, lean, mean and kde machine, Konqueror and is KHTML engine!!!

But wait a minute, isn’t KHTML somewhat diferent from webkit? Well.. yes and no, webkit WAS based in KHTML, so for testing purposes (not to mention merit) we included KHTML in our review, but there’s a somewhat more hidden reason also. You see, Konqueror has a webkit kpart so you can switch between khtml and webkit on-the-fly, and THATS the primary reason we added good old konki to the review 🙂

Lets see how every browser likes to be called. We used w3schools to ask them nicely, and this is what konki told us:

Mozilla/5.0 (compatible; Konqueror/4.2; Linux) KHTML/4.2.2 (like Gecko)

Now lets torture.. i mean ask nicely the webkit part:

Mozilla/5.0 (Konqueror/4.2; Linux) AppleWebKit/527+ (KHTML, like Gecko, Safari/419.3)

Ok, so how this two compare in real tests? We put them to the test with acid3, flash 10 and a javascript benchmark, and from where we are standing, old konki is in pretty good shape. As you can all see from the screenshot below, the more acid konki drinks the better it gets 😀 It now almost passes the test.

Acording to the dealer, konki fails with the acid because of this:

Failed 13 tests.

Test 13 failed: collapsed is wrong after deletion

Test 26 failed: e1 – parent element doesn’t exist after looping

Test 27 failed: e1 – parent element doesn’t exist after waiting

Test 29 failed: expected ‘2’ but got ‘1’ – cloned table had wrong number of children

Test 31 passed, but took 35ms (less than 30fps)

Test 40 passed, but took 34ms (less than 30fps)

Test 51 failed: expected ‘6’ but got ‘5’ – wrong number of rows

Test 53 failed: expected ‘1’ but got ‘0’ – form’s elements array has wrong size

Test 54 passed, but took 34ms (less than 30fps)

Test 69 passed, but took 70 attempts (less than perfect).

Test 70 failed: UTF-8 encoded XML document with invalid character did not have a well-formedness error

Test 74 failed: getSVGDocument missing on <iframe> element.

Test 75 failed: SVG DOM interface SVGRectElement not supported.

Test 76 failed: Undefined value

Test 77 failed: SVGTextContentElement.getNumberOfChars() not supported.

Test 78 failed: Attempt to use a non-function object or a value as a function.

Test 79 failed: Attempt to use a non-function object or a value as a function.

Total elapsed time: 11.28s

The webkit kpart performs a little better, but still isn’t perfect (keep reading and you’ll be shocked on how many browsers pass the test flawlessly).

Here are the scores:

Failed 2 tests.

Test 00 passed, but took 156ms (less than 30fps)

Test 01 passed, but took 42ms (less than 30fps)

Test 26 passed, but took 112ms (less than 30fps)

Test 65 passed, but took 94ms (less than 30fps)

Test 69 failed: timeout — could be a networking issue

Test 74 failed: getSVGDocument failed for <object> referencing an svg document.

Test 75 passed, but took 73ms (less than 30fps)

Total elapsed time: 9.48s

But in real life, both browsers perform very well and konki as a feature none of the other webkit browser have, the versatility. Since one image speaks for a thousand words and we are lazy, here it is what we mean:

At the upper left we have the khtml kpart running a acid3 test, and below we have a filemanager kpart, to the left we have the webkit kpart running the same acid3 and to top it all, on the bottom we have a console kpart. Try that with any other browser/filemanager 😀 Finally, when it come to javascript, KJS used by KHTML is starting to show is age, being the slowest of them all, but the kpart webkit really shines and is the fastest of the bunch, losing only to one browser (guess who?) 😉

Next kid is a peach 😀 Is name is arora, is qt/kde based and it works very well indeed. It’s our favorite of all the webkit browsers till now.

It insists after questioned that is name is:

Mozilla/5.0 (X11; U; Linux; en-US) AppleWebKit/527+ (KHTML, like Gecko, Safari/419.3) Arora/0.6

Arora passes the acid3 test but has a few caveats with some rendering taking more then 50ms (less then 30fps), hence the linktest failed, it has flash and is very fast and stable, and it opens in a snap. In the javascript speed test it isn’t the slowest nor the fastest.

Next in the bunch comes our gtk based favorite, midori.

Identified by this name, is the only that passed the acid3 test flawlessly, probably because its the one with the newest webkit engine as you can see:

Mozilla/5.0 (X11; U; Linux i686; en-us) AppleWebKit/528.5+ (KHTML, like Gecko, Safari/528.5+) midori

The dealer says:

Failed 0 tests.

Test 26 passed, but took 87ms (less than 30fps)

Test 69 passed, but took 89 attempts (less than perfect).

Test 79 passed, but took 54ms (less than 30fps)

Total elapsed time: 9.47s

Picky, Picky… no one seems to please the acid dude. Midori also has a plugin system similar to firefox addons and it is a fairly complete and stable browser. When it comes to javascript its also one the fastest.

Next we have a midori cousin from the east, kazehakase, which besides the unpronounceable name has the differential of being the only hybrid browser of the bunch (he can use both gecko and webkit engines, a feat on its own), but is still a little slow and rough around the edges. A nice browser nonetheless.

Passport card shows him as a:

Mozilla/5.0 (X11; U; Linux i686; en-us) AppleWebKit/525.1+ (KHTML, like Gecko, Safari/525.1+) kazehakase

He also has acid3 on its veins:

Failed 0 tests.

Test 26 passed, but took 98ms (less than 30fps)

Test 69 passed, but took 73 attempts (less than perfect).

Total elapsed time: 3.34s

We are now down to two browsers, the youngest of the bunch, the babies of the pack, ladies and gentlemen, please welcome…

reKonq is a baby browser with a lot of promise. based on QTWebDemo just like arora, is aim is to be a full feature KDE browser, and already has a few interesting tricks, like being a singleton app (if a tab crash it doesn’t bring the browser down with it, just like google chrome). It is also very fast and just like arora and the bunch, supports flash and performs very well in day to day usage). We are going to keep a very close eye on this kid as he matures.

After asking if he likes mommy or daddy more, he answered:

Mozilla/5.0 (X11; U; Linux; en-US) AppleWebKit/527+ (KHTML, like Gecko, Safari/419.3) rekonq

The kid also isn’t old enough for acid3, but he’s getting there:

Puff daddy would be proud:

Since it doesn’t know how to run yet, he’s not the fastest in the javascript test, but being young gives him some edge, so he isn’t the slowest either. Overall, reKonq poses itself as one of the best browsers in potencial, so keep watching for this little guy, it might even surprise you.

Finally, we have the youngest browser, the javascript test champion, and most hyped browser on earth. A great salve of applause to:

CHROMIUM!!! The google chrome open source cousin already is developing nicely…

The ultrascan shows he is a:

Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/530.7 (KHTML, like Gecko) Chrome/ Safari/530.7

Unfortunately to the youth organizations he’s already on acid:

And this medical records show there is no hope for the little fella, he’s addicted already:

Failed 0 tests.

Test 26 passed, but took 106ms (less than 30fps)

Total elapsed time: 1.34s

Chromium doesn’t support flash yet, or any plugin for that matter, it doesn’t have proxy support yet, or a options menu, or a bookmarks manager, or almost anything you would encounter in a modern browser. But it will eventually, it already has working tabs, download bar and history with search.

And it’s faaaaaaaaast, we mean, REAL faaaaaaaaaaaast. It’s the javascript fastest of the bunch, and very slick with gmail and other heavy javascript homepages. Definitely a winner when its ready.


From this score and graphics, you can see that the javascript speed is very diferent from similar engines and browsers, and a lot of testing and tweaking is yet to be achieved.

This is the score for the SunSpider Javascript Benchmark









Konqueror (webkit)








Complete with bar chart 🙂

Lower is better

The webkit linux browser ecosystem is very much alive and well, with a lot of interesting features and innovation coming along.

We look forward to review this bunch again in about 6 months and see how they grew and how successful they have become.

Thanks for reading.

Posted in Uncategorized | 4 Comments

Amarok 2.1 – back to the future. (versão em Português)

A equipe padoca é fã do Amarok à muito tempo. Nós vimos o pequeno amarok crescer e tornar-se o melhor media player durante a série 1.x. Nós vislumbramos a promessa e potencial aquando da versão 2.0, a mesma promessa e potencial que marcou o lançamento do Kde 4.0

Uma reescrita, um novo começo, imperfeito no início mas cheio de visão e potencial. Claro, faltam features (como faltavam no kde 4.0) mas foi um mal necessário. Para poderem concretizar o futuro vislumbrado pela equipe de desenvolvimento do amarok, eles precisavam voltar… Precisaram mandar o amarok de volta no tempo… e isso transpareceu.

Agora o amarok 2.1 está a desenvolver-se no svn, crescendo, começando a mostrar o seu potencial. Esta é uma saga de crescimento e aprendizado. O futuro está chegando!

Então, o que tem de novo no 2.1? MUITA coisa!

Vamos começar pelo interior, está bem?

  • O Amarok 2.1 agora suporta replaygain (nos modos track e álbum).

  • Esta é uma das minhas adições favoritas. Eu costumava usar e abusar do script replaygain na série 1.x do amarok, e agora esta grande feature está disponível nativamente no Amarok 2.1, usando um mix de magia e Taglib.
    Até agora o amarok 2.1 consegue LER tags do replaygain em praticamente qualquer arquivo de áudio que lhe mandarem na fuça. Os devs estão debatendo se e quando deveriam adicionar suporte a ESCRITA nas tags, mas até agora os amarokers podem usar o excelente (kde3) soundKonverter para escrever as tags nas suas coleções favoritas.

    Hum, tio? O que exatamente é essa parada aí de “replaygain”?

    Boa pergunta! Por acaso já lhe aconteceu de estar escutando uma música calma, alguma coisa como marisa monte ou enya e de repente seus tímpanos irem parar no apartamento do lado, pq o seu player pulou para um prodigy a todo volume ou pra quem gosta, um funk pancadão? Pois é, se vc não consegue escutar mais nada sem ajuda auricular é porque NÃO usou o replaygain. Porque o que ele faz é analisar os arquivos de áudio e calcular um nível de decibeis ótimo para cada um, assim quando vc tocar os mesmos, o amarok possa ler esse dado e mudar o volume de acordo com cada um, preservando a sua capacidade auricular.

  • Capacidade de editar a playlist.

    Esta trouxe um pouco de alegria ao meu coração negro. Eu utilizava muito a playlist na série 1.x, e digamos que a capacidade da versão 2.0 é hmmm.. fraca. Quando eu vi esta maravilhada da tecnologia moderna, até pensei em parar de matar gatinhos!

    Agora as playlists podem ser customizadas usando um editor simples mas poderoso, e esta solução é a melhor que já vi em qualquer player. Não acredita, então veja os screenshots e o vídeo.

    Este vídeo mostra o editor em ação.

    Este screenshot mostra o editor mudando a playlist em modo track (vc também pode editar o modo álbum).

  • O plasmoid de trilhas agora mostra as últimas e as favoritas.

  • O serviço Last.FM foi completamente reescrito e é agora o mais poderoso cliente do last.fm (ainda mais do que o cliente oficial).
    Ele pode tocar todos os tipos de estações mostrado abaixo sem precisar de uma conta paga.

    Agora a configuração do last.fm tem uma opção que checa o usuário e senha do serviço e funciona com o proxy do kde (o serviço também).

  • A interface dos plasmoids foi refeita.

    Os plasmoids continuam a residir na parte central mas agora ao invés de residirem em 4 desktop virtuais, todos residem numa coluna central, e podem ser ativados/desativados por meio de uma taskbar embaixo dos mesmos.
    Vejam o vídeo e os screenshots para um melhor entendimento.

  • Plasmoid de serviços.

    Este é um plasmoid muito legal e praticamente saído do forno, foi adicionado à poucos dias. Basicamente, quando vc escolhe um serviço como o Jamendo ou Magnatune, ele se conecta aos mesmos e mostra informações relevantes do item escolhido. Vejam screenshots e vídeo.

    Este mostra o serviço já conectado ao website do jamendo e mostrando a informação de uma música.

    Este mostra o serviço em modo espera.

  • O amarok tem muito amor para dar, e agora todas as trilhas podem ser amadas, não apenas aquelas que vieram do last.fm.

  • Amarok urls.

    O amarok agora pode carregar e gerar “amarok urls” que permitam gravar num bookmark qualquer “visão” e posteriormente carregar a mesma. Um protocolo foi tb desenvolvido e instalado que permite lançar o amarok com o status correto quando chamado externamente.

  • Conclusão.

    O amarok 2.1 ainda vai ver MUITO desenvolvimento antes da versão final. O tamanho do código sendo desenvolvido é impressionante, e pelo que vimos até agora, o amarok 2.1 será o melhor até agora.


Posted in Uncategorized | 9 Comments

Amarok 2.1 – back to the future. (english version)

We (padoca team) are long time Amarok users. We have seen amarok grow and become the best audio player along the 1.x series. We’ve seen the writing on the wall when 2.0 was out, the same promise and potential that embodied Kde 4.0 release.

A rewrite, a new beginning, not perfect at first but full of potential and vision. Sure, some features where sorely missed (like Kde 4.0) but it was needed. In order to be able to make the future envisioned by the amarok dev team, they had to go back… they had to send amarok back in time, and it showed.

Now amarok 2.1 is shaping up in svn, growing, showing his potencial. This is his tale of growth and learning. The future is coming!

So, what’s new within 2.1? A lot!

Lets start with the inner guts, shall we?

  • Amarok 2.1 now suports replaygain (both track and album mode).

    This is one of my favorites aditions. I used to abuse the replaygain script in the 1.x series, and now this great feature is suported natively by amarok 2.1, using a mix of taglib and other magics.
    Till now amarok can READ replaygain tags for pretty much every audio format you can throw at him.
    The devs talked a little of ways of adding write support (reading non tagged files and calculating the replaygain) like a plasmoid and such, but for now, amarokers can use the excelent (kde 3) soundKonverter for writing replaygain tags for their collections.

    Hum? Master… What exactly is “replaygain”?

    Well little grasshoper, have you ever listened to a track, some nice, slow, calm track like enya, only to get your hears blown out from the next prodigy track which had a much higher volume? If you CAN’T hear me, you probably did. So this is what replaygain does, he analyses the tracks and calculates an optimum decibel for each one, so when amarok reads the tracks he knows if he must change the volume to preserve your hearing capabilities.

  • Editable Playlists.

    This one brought some tears to my cold, harsh eyes. You see, i’m a playlist freak, i like to mix and match a lot of info, and the playlist in 2.0.x was, well, cumbersome at best, so when i’ve seen this beauty of modern technology in svn, i almost cryed.

    Now playlists can be costumized using a powerful yet simple editor, and this solution is the best i’ve seen for any player. Don’t believe me? Watch the video and the screenshots.

    The video shows what you can do with the editor.

    This screenshot shows the editor changing the playlist in single track mode (you can also change the playlist in album mode).

  • The current track plasmoid now shows current and favorite tracks.

  • The Last.FM service was completely rewritten and now is the most powerful client for last.fm (even more then the oficial last.fm one).
    It can now play all the kind of tracks displayed below without a payed account, even My Recomendations and My Radio Station.
    See for yourself.

    Also, the last.fm settings now have a way to check if your user and password is correct and even works behind the kde proxy settings.

  • Plasmoid Interface revamp.

    Plasmoids continue to reside in the central space BUT, now instead of being scatered in 4 separate virtual folders, they reside in a single column, and can be switched/choosed with a new taskbar in the lower central window. See the video and screenshot for a better understanding of what i’m talking about.

  • Services Plasmoid.

    This is a very cool idea/plasmoid that was added just a few days ago. When you choose a service, like jamendo, it will connect to the service site and match the info you are choosing with the one you have online, real cool. See screens and video.

    This one shows the service already conected to the jamendo website and showing a track info.

    This one shows the service in “waiting” mode.

  • Amarok has a lot of love to give, and the new love feature for ALL tracks shows he means business. Now amarok loves all tracks, not only last.fm ones.

  • Amarok urls.

    Amarok can now load and generate “amarok urls” that allows any “view” to be bookmarked and later retrieved. A protocol handler is also installed that will launch amarok into the correct state, or make amarok show the correct view if already running if such a url is activated system wide.

  • Rants.

    They aren’t exactly rants, we sure liked everything so far, and overall the 2.1 svn already is our player of choice. But, as a long time amarok users we have some ideas/complaints we would like seeing adressed sooner then later. We aren’t going to rant (amarok 1.x had blah blah blah), that’s not the idea, we wan’t to contribute with tips and requests most power user have (and amarok devs are probably aware already, since they are power users too), but without telling them how to do they jobs. Like they’ve proven more then once (the playlist editor is one of many examples) , they know how to implement in the best way possible. So let’s us ask and be given 😉

    1. Separate views.

      Plasmoids are great, playlists are great, colections are great, but we can only have that much screen real estate.
      We think amarok should have separate view for the task the use is doing, somethins like:

      • admin mode for editing/adding plasmoid, adding visualizations (when they come available) and such.
      • play mode with a playlist, visualizations, equalizers, MediaFlow, mashTape and more.
      • colection mode with all colection related stuff, like cover flow administration, picard integration with the tag editor maybe with a plasmoid implementation.
    2. More eye candy.

      Return of the mood bar, return of visualizations, implementation of MediaFlow alike (we’ve seen something like that in the svn before 2.0 was released).
      Eye candy is important and amarok devs are aware of it, but there’s a lot to do, and we’ll see a lot coming out in the next releases, we just wrote this so they don’t forget 😉

    3. More ways to interact with your music, like equalizers and other modern audio goodies (like karaoke).
    4. Insert you wish here… Amarok is one of the best known and exposed open source audio player, wishes are fine, just don’t forget they do it for free. be polite and if you can send patches.
  • Conclusion.

    Amarok 2.1 still will see a LOT of development before the final version. The cheer amount of code thrown around is quite impressive, and for what we can gather so far, amarok 2.1 will probably be the best release ever.
    We just wish some of the rants will be listened and adressed somewhere, somehow.

That’s ALL folks!

Posted in Uncategorized | 26 Comments

cedilhas no kde / (K)ubuntu reloaded.

Os croatas escondidos na áfrica do sul voltaram a atacar, e novamente destruiram a cedilha no utf-8 (que o (k)ubuntu usa por padrão), para que possamos voltar a escrever o ç ao invés do ć aqui vai a receita de bolo.

sudo apt-get install language-pack-pt
cd /usr/share/locales
sudo ./install-language-pack pt_BR
sudo ./install-language-pack en_US

  • Edite o arquivo /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules.
  • Adicione “en” na lista teclados no módulo “cedilla”.
  • Agora, edite o arquivo Compose em /usr/share/X11/locale/en_US.UTF-8
  • Substitua o ć com ç em todas as entradas desse arquivo.
  • Por fim, adicione uma linha em /var/lib/locales/supported.d/en com o seguinte conteúdo:
  • en_US.ISO-8859-1 ISO-8859-1
  • Isso mesmo, ISO-8859-1 duas vezes.

Reinicie… e tenha ççççç de sobra no kde/gnome.


Posted in Uncategorized | Leave a comment