Há alguns dias atrás eu havia convocado a todos para colaborar com fotos para o concurso de papeis de parede do Ubuntu GNOME 14.04. Agora tenho o prazer de convidar vocês agora para a etapa final do concurso de papeis de parede do Ubuntu GNOME! Chegou a hora de escolher os melhores papeis de parede que serão utilizados na versão final do Ubuntu GNOME 14.04.
A votação se dará até o dia 09/03/2014. Dentre os papeis de parede, escolha os 10 (dez) melhores, esta será a quantidade finalista!
Para votar, basta clicar no botão abaixo:Concurso de melhores papeis de parede
Em breve anunciarei aqui os grandes vencedores! Desde já, eu e o Time de arte do Ubuntu GNOME agradecemos o seu voto!
Obs.: Este post é melhor visualizado acessando direto da fonte: Blog do Ubuntuser
Originalmente publicado no PoliGNU.
Por quê mudar?
kov@melancia ~> systemctl status mariadb.service mariadb.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled) Active: active (running) since Seg 2014-02-03 23:00:59 BRST; 1 weeks 3 days ago Process: 6461 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS) Process: 6431 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS) Main PID: 6460 (mysqld_safe) CGroup: /system.slice/mariadb.service ├─6460 /bin/sh /usr/bin/mysqld_safe --basedir=/usr └─6650 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plug... Fev 03 23:00:57 melancia mysqld_safe: 140203 23:00:57 mysqld_safe Logging to /var/log/mariadb/mariadb.log. Fev 03 23:00:57 melancia mysqld_safe: 140203 23:00:57 mysqld_safe Starting mysqld daemon with databas...mysql Fev 03 23:00:59 melancia systemd: Started MariaDB database server. Hint: Some lines were ellipsized, use -l to show in full.
A questão de licenciamento
O time de arte do Ubuntu GNOME resolveu incluir papéis de parede da comunidade para o lançamento do Trusty Tahr (14.04). Chegou a hora de você colaborar para embelezar ainda mais o Desktop de milhões de usuários nesta próxima versão do Ubuntu GNOME.
Algumas instruções devem ser seguidas para o concurso:
- Sem marcas comerciais, nome de marcas, armas, violência, imagens pornográficas ou sexualmente explícitas;
- Evitar imagens de movimentos, e também de com muitas formas e cores;
- Pode ser utilizado um único ponto de foco;
- Os elementos do GNOME Shell devem ser levados em consideração durante a criação;
- A dimensão final deverá ser de 2560 x 1600 pixels;
Processo de envio
O processo de envio será através da Wiki do Ubuntu, então basta ter uma conta no Launchpad! O que você está esperando para começar a enviar a sua obra de arte? Para maiores informações sobre como é todo esse processo, basta clicar nos botões abaixo:Como enviar | Página de envio
When a new year comes, it’s time to reflect (not regret) and set up new goals.
For 2014, I want to intensify my GNOME contributions, read 50 books, graduate o/*, and (after that) find a first job.
I’m just back from a well deserved 2-week vacation in Salvador—the city where I was born and raised. While in Brazil, I managed to stay (mostly) offline. I intentionally left all my gadgetry at home. No laptop, no tablet. Only an old-ish smartphone with no data connection.
Offline breaks are very refreshing. They give you perspective. I feel we, from tech circles, are always too distracted, too busy, too close to these things.
Stepping back is important. Idle time is as important as productive time. The world already has enough bullshit. Let’s not make it worse.
Here’s for a more thoughtful, mindful, and meaningful online experience for all of us. Happy new year!
In the last weeks I’ve been working on GTK+ themes, customizing some apps, and I missed the tools we have on the web world that allow us to to some live editing on CSS.
I remembered we had Parasite, a tool similar to Firebug, but for GTK+ apps. Unfortunately it didn’t support CSS tweaking. But it does now! I’ve made some improvements on it mainly to allow live editing of CSS, but not limited to that.
Some changes so far:
- Live editing of CSS, for the whole application, or only for the selected widget
- Ability to add/remove a CSS class for a specific widget. (Editing of pseudo-classes like :hover is planned)
- In the Property inspector, if a property itself is another Object, we can also inspect it. (For example, you can inspect a Buffer inside a TextView)
- A bit of UI change
I have made a small video showing the improvements:
Link to the video
The code is on the usual place, github: https://github.com/chipx86/gtkparasite
Please, test it and file bugs/wishes/pull requests. /me is now wearing the maintainer hat
Note: it requires GTK+ 3.10 (and optionally python+gobject introspection for the python shell)
Essa dica vai para quem tem notebooks Presario, Toshiba, etc… Vamos instalar a sua placa de rede Wifi?
Primeiramente, confirme a versão do seu kernel, executando no seu terminal:
Caso a versão do mesmo, seja uma das versões informadas acima, vamos então dar continuidade ao processo.
1. Clonar o diretório do GIT. Caso não tenha o git instalado na sua máquina, execute:
sudo apt-get install git
2. Agora, vamos clonar (É feita uma cópia do código fonte para a sua máquina):
cd ~ && git clone https://github.com/FreedomBen/rtl8188ce-linux-driver.git
Note que foi criada uma pasta chamada rtl8188ce-linux-driver na pasta do seu usuário.
3. Instalar as dependências de compilação (preste atenção aos crases!):
sudo apt-get install gcc build-essential linux-headers-generic linux-headers-`uname -r`
4. Acesse o diretório e vamos começar a compilar:
cd ~/rtl8188ce-linux-driver && make
Obs.: Caso seja informado algum erro, confirme se o branch é realmente o da sua versão. Por exemplo: Se a sua versão do Ubuntu for a 13.10, execute:
git checkout ubuntu-13.10
Após executar o checkout para o branch correto da sua versão, execute o passo 4 novamente.
sudo make install
6. Ative (modprobe) o novo driver:
sudo modprobe rtl8192ce
(Este é o driver da rtl8188ce também)
7. Você pode precisar modprobe volta nos outros módulos também. Basta repetir o passo 6, alterando para os:
rtl8192ce, rtlwifi, e rtl8192c_common
Torne permanente, adicionando isto ao final do /etc/modules:
Para editar e acrescentar a linha acima no /etc/modules, execute:
sudo gedit /etc/modules
Pronto! Placa de rede instalada. Reinicie o sistema e voilá!
Agradecimentos especiais a FreedomBen
For the fifth year in a row the fearless WebKitGTK+ hackers have gathered in A Coruña to bring GNOME and the web closer. Igalia has organized and hosted it as usual, welcoming a record 30 people to its office. The GNOME foundation has sponsored my trip allowing me to fly the cool 18 seats propeller airplane from Lisbon to A Coruña, which is a nice adventure, and have pulpo a feira for dinner, which I simply love! That in addition to enjoying the company of so many great hackers.
The goals for the hackfest have been ambitious, as usual, but we made good headway on them. Web the browser (AKA Epiphany) has seen a ton of little improvements, with Carlos splitting the shell search provider to a separate binary, which allowed us to remove some hacks from the session management code from the browser. It also makes testing changes to Web more convenient again. Jon McCan has been pounding at Web’s UI making it more sleek, with tabs that expand to make better use of available horizontal space in the tab bar, new dialogs for preferences, cookies and password handling. I have made my tiny contribution by making it not keep tabs that were created just for what turned out to be a download around. For this last day of hackfest I plan to also fix an issue with text encoding detection and help track down a hang that happens upon page load.
Martin Robinson and myself have as usual dived into the more disgusting and wide-reaching maintainership tasks that we have lots of trouble pushing forward on our day-to-day lives. Porting our build system to CMake has been one of these long-term goals, not because we love CMake (we don’t) or because we hate autotools (we do), but because it should make people’s lives easier when adding new files to the build, and should also make our build less hacky and quicker – it is sad to see how slow our build can be when compared to something like Chromium, and we think a big part of the problem lies on how complex and dumb autotools and make can be. We have picked up a few of our old branches, brought them up-to-date and landed, which now lets us build the main WebKit2GTK+ library through cmake in trunk. This is an important first step, but there’s plenty to do.
Under the hood, Dan Winship has been pushing HTTP2 support for libsoup forward, with a dead-tree version of the spec by his side. He is refactoring libsoup internals to accomodate the new code paths. Still on the HTTP front, I have been updating soup’s MIME type sniffing support to match the newest living specification, which includes specification for several new types and a new security feature introduced by Internet Explorer and later adopted by other browsers. The huge task of preparing the ground for a one process per tab (or other kinds of process separation, this will still be topic for discussion for a while) has been pushed forward by several hackers, with Carlos Garcia and Andy Wingo leading the charge.
Other than that I have been putting in some more work on improving the integration of the new Web Inspector with WebKitGTK+. Carlos has reviewed the patch to allow attaching the inspector to the right side of the window, but we have decided to split it in two, one providing the functionality and one the API that will allow browsers to customize how that is done. There’s a lot of work to be done here, I plan to land at least this first patch durign the hackfest. I have also fought one more battle in the never-ending User-Agent sniffing war, in which we cannot win, it looks like.
I am very happy to be here for the fifth year in a row, and I hope we will be meeting here for many more years to come! Thanks a lot to Igalia for sponsoring and hosting the hackfest, and to the GNOME foundation for making it possible for me to attend! See you in 2014!
This was a year of consolidation for us, and I think we’ve succeeded in getting Firefox for Android in a much better place in the mobile browser space. We’ve gone from an (embarrassing) 3.5 average rating on Google Play to a solid 4.4 in just over a year (!). And we’re wrapping up 2013 as a pre-installed browser in a few devices—hopefully the first of many!
We’ve just released Firefox for Android 26 today, our last release this year. This is my favourite release by a mile. Besides bringing a much better UX, the new Home screen lays the ground for some of the most exciting stuff we’ll be releasing next year.
A lot of what we do in Firefox for Android is so incremental that it’s sometimes hard to see how all the releases add up. If you haven’t tried Firefox for Android yet, here is my personal list of things that I believe sets it apart from the crowd.
All your stuff, one tap
The new Home in Firefox for Android 26 gives you instant access to all your data (history, bookmarks, reading list, top sites) through a fluid set of swipable pages. They are easily accessible at any time—when the app starts, when you create a new tab, or when you tap on the location bar.
You can always search your browsing data by tapping on the location bar. As an extra help, we also show search suggestions from your default search engine as well as auto-completing domains you’ve visited before. You’ll usually find what you’re looking for by just typing a couple of letters.
Great for reading
Firefox for Android does a couple of special things for readers. Every time you access a page with long-form content—such as a news article or an essay—we offer you an option to switch to Reader Mode.
Reader Mode removes all the visual clutter from the original page and presents the content in a distraction-free UI—where you can set your own text size and color scheme for comfortable reading. This is especially useful on mobile browsers as there are still many websites that don’t provide a mobile-friendly layout.
Secondly, we bundle nice default fonts for web content. This makes a subtle yet noticeable difference on a lot of websites.
Last but not least, we make it very easy to save content to read later—either by adding pages to Firefox’s reading list or by using our quickshare feature to save it to your favourite app, such as Pocket or Evernote.
Make it yours
If you’re into blingy UIs, you can install some lightweight themes. Furthermore, you can install and use any web search engine of your choice.
Smooth panning and zooming
An all-new panning and zooming framework was built as part of the big native rewrite last year. The main focus areas were performance and reliability. The (mobile) graphics team has released major improvements since then and some of this framework is going to be shared across most (if not all) platforms soon.
From a user perspective, this means you get consistently smooth panning and zooming in Firefox for Android.
We develop Firefox for Android through a series of fast-paced 6-week development cycles. In each cycle, we try to keep a balance between general housekeeping (bug fixes and polishing) and new features. This means you get a better browser every 6 weeks.
Open and transparent
Firefox for Android is the only truly open-source mobile browser. There, I said it. We’re a community of paid staff and volunteers. We’re always mentoring new contributors. Our roadmap is public. Everything we’re working on is being proposed, reviewed, and discussed in Bugzilla and our mailing list. Let us know if you’d like to get involved by the way :-)
That’s it. I hope this post got you curious enough to try Firefox for Android today. Do we still have work to do? Hell yeah. While 2013 was a year of consolidation, I expect 2014 to be the year of excitement and expansion for Firefox on Android. This means we’ll have to set an even higher bar in terms of quality and, at the same time, make sure we’re always working on features our users actually care about.
2014 will be awesome. Can’t wait! In the meantime, install Firefox for Android and let us know what you think!
Habilitando o repositório de atualizações de pré-lançamentos no Ubuntu, normalmente não é uma boa ideia porque esta é uma área de testes para as atualizações, então algo pode quebrar. Se você habilitou este repositório e algo deu errado, aqui você saberá como reverter as alterações através da desatualização dos pacotes instalados através do repositório de atualizações de pré-lançamentos.
Revertendo as atualizações de pacotes do repositório de atualizações de pré-lançamentos
1. Primeiramente carregue Programas e atualizações (Nas versões mais antigas do Ubuntu, vá em Gerenciador de atualizações e clique em Configurações), clique na aba Atualizações e desabilite a opção Atualizações de pré-lançamento (proposed):
2. Em seguida devemos fixar os pacotes do repositório do Ubuntu: Para estável, atualizações importantes de segurança, recomendadas e não suportadas, usaremos uma prioridade maior do que 1000, o que fará com que os pacotes a partir desses repositórios sejam instalados, mesmo se isto constituir um downgrade e para o repositório de pré-lançamento, vamos definir uma prioridade menor que 0, impedindo que os pacotes sejam instalados.
Para fazer isso, crie um arquivo chamado “99-downgrade-proposed” em /etc/apt/preferences.d/ – Vamos usar Gedit:
gksu gedit /etc/apt/preferences.d/99-downgrade-proposed
E no arquivo, copie e cole o seguinte:
Package: * Pin: release a=saucy Pin-Priority: 1001 Package: * Pin: release a=saucy-updates Pin-Priority: 1001 Package: * Pin: release a=saucy-security Pin-Priority: 1001 Package: * Pin: release a=saucy-backports Pin-Priority: 1001 Package: * Pin: release a=saucy-proposed Pin-Priority: -1
Observação: Substitua o “saucy” pela sua versão do Ubuntu no lista acima. Em seguida, salve o arquivo.
3. Agora podemos iniciar o processo de downgrade, executando os comandos abaixo:
sudo apt-get update sudo apt-get dist-upgrade
Verifique se o “dist-upgrade” não removerá todos os pacotes importantes. Se tudo estiver ok, prossiga com o downgrade.
4. Após o downgrade, você pode remover o arquivo criado no passo 2:
sudo rm /etc/apt/preferences.d/99-downgrade-proposed
Até a próxima!
Fonte: WEB UPD8