Skip to main content

the avatar of Gabriel Burt

Banshee Release Schedule

We are aligning Banshee's release schedule with GNOME's, at least for the next few months. Banshee 1.6 will be released the same day as GNOME 2.30, and we'll have three beta releases before then.
  • 1.5.3 - Jan 27 - Wednesday!
  • 1.5.4 - Feb 24
  • 1.5.5 - Mar 10 - String Freeze
  • 1.6.0 - Mar 31
I'm excited to try switching our schedule from feature and whim driven to time-based; I think it will be felt positively by everybody: contributors will know when their work will reach people, translators will have time to translate, and users can stop wondering what mixture of magic and bribes will cause a release to finally happen.

Subscribe to the Banshee development calendar, find out how to help test the latest Banshee, and/or contribute your creativity and sweat!
a silhouette of a person's head and shoulders, used as a default avatar

FOSDEM 2010

Just 9 Days away from the start of FOSDEM. The start of a new year and with it the start of new opportunities. This will be my first FOSDEM and my first big event with Fedora...

The Ambassador team in the Netherlands has been preparing for a number of months for this event and the opportunities that it will yield for us and more importantly for the greater FOSS community. I can only expect great new ideas and projects, since now Industries and Governments are starting to see the big picture of FOSS and Open source due to access to resources, as well as, the value-added factors of low-cost and organizational sustainability.

Recently, there have been a lot of changes and focus on "All things open" where many public authorities are finally admitting that they "Do not have all the answers" or "Enough Human Resources" to sustain their systems. In addition, many non-profit and for-profit organizations are adopting communities to enhance and or jump start innovations to contribute to their long-term sustainability.

I believe that 2010 will be the year of "All Things Open" and look forward to sharing ideas, initiating projects, promoting and supporting the development of a better society, world and planet, not only for ourselves, but for our future generations.

See you at FOSDEM!!
a silhouette of a person's head and shoulders, used as a default avatar

Update without root password?

In the old days of openSUSE 10.x I used sudo and its configuration to install updates and new software in GUI without the most-annoying (I know, secure) need to enter password of root. Since version 11, this is no longer possible.

Since I am too lazy to enter root password (I've already logged-in, it's me, right?), I spent quite some time figuring out how to solve it. And I finally did.

In KDE the kupdateapplet is used to check for updates. In default installation kupdate applet uses PackageKit backend. To make things more complicated, PackageKit uses another framework: PolicyKit. (From What's PackageKit?: "The primary design goal is to unify all the software graphical tools used in different distributions, and use some of the latest technology like PolicyKit to make the process suck less." - WTF?! I wanna sudo!).

How does it work? When the update applet issue update command to PackageKit, PackageKit asks PolicyKit for permission. PolicyKit checks it's configuration and either allows it, denies it, or ask for authentication (enter password). If you want to know how it works, read the PolicyKit and PackageKit documentation.

What we need to do is configure PolicyKit in a way that it gives permission to update action of PackageKit.

Default permissions are stored in file /etc/polkit-default-privs.standard (or /etc/polkit-default-privs.restrictive according to value of POLKIT_DEFAULT_PRIVS in /etc/sysconfig/security). The file have following syntax:

action_id permissions

or (one line)

action_id&nbsp perm_any_user:perm_user_not_on_the_active_console:perm_user_on_the_active_console

In first case, same permission are applied. In second case different permission are used for user on active console, etc.

Possible permissions are:

  • yes allowed
  • no denied
  • auth_admin need root password
  • auth_admin_keep same as above, but will not require password again for some time
  • auth_user need user password
  • auth_user_keep same as above, but will not require password again for some time

Action IDs and their descriptions can be found in files located in /usr/share/polkit-1/actions/. The one we're looking for is: org.freedesktop.packagekit.system-update.

In our case, we want that user on active console don't have to enter root password for installation of updates. So we add following rule to /etc/polkit-default-privs.local (do not modify polkit-default-privs.standard and polkit-default-privs.restrictive since they may be overwritten during some update!):

org.freedesktop.packagekit.system-update auth_admin:auth_admin:yes

And we need to install the privileges to the system (without following command, it won't work):

/sbin/set_polkit_default_privs

Yes! Now you should be able to update your system without the need to enter root password.

Same way can be used for package installation, removal, etc. You can also ask user to enter his password instead of root password. The only thing I miss is Vista-like way: make user explicitly click "I know what I'm doing" without the need to enter password. Why? Because this way some script can install a package on your system without you even knowing it (If you have passwordless installation allowed for user on active console and the user runs the script without knowing what it exactly does. But I didn't test it, maybe it doesn't work this way? Maybe there's some check?)

Special thanks to Ludwig Nussel for pointing me to /sbin/set_polkit_default_privs.

the avatar of Carlos Gonçalves

a silhouette of a person's head and shoulders, used as a default avatar

Fixing Lighttpd in Debian on SheevaPlug

I was using SheevaPlug as my Home NAS, with and external usb hdd, until recently when I built my new NAS, based on ION ATOM, FreeBSD and ZFS.

I am thinking to add an usb webcam and to use it as a monitoring system.

I updated Debian "squeeze", which is running on an 8G SDHC card, but I got the error:

*After this operation, 0B of additional disk space will be used.  
Do you want to continue [Y/n]? y  
Setting up lighttpd (1.4.25-2) ...  
Starting web server: lighttpd2010-01-22 23:13:31: (network.c.345) can't
bind to port: :: 80 Address already in use  
failed!  
invoke-rc.d: initscript lighttpd, action "start" failed.  
dpkg: error processing lighttpd (--configure):  
subprocess installed post-installation script returned error exit
status 1  
Errors were encountered while processing:  
lighttpd  
E: Sub-process /usr/bin/dpkg returned an error code (1)  
sheeva:/home/ionut\#*

I didn't have anything running and listening on port 80, so, it seems that it is a known bug, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564556 and the solution is here:

Add in /etc/lighttpd/lighttpd.conf:

*server.use-ipv6 = "enable"*

And add in /etc/sysctl.d/bindv6only.conf:

"*net.ipv6.bindv6only = 0*"
a silhouette of a person's head and shoulders, used as a default avatar

GNOME 2.28.2 on openSUSE 11.2 Updates more packages for openSUSE

Today the openSUSE GNOME team released the GNOME 2.28.2 update for 11.2. This also shows a different direction in openSUSE that is more user community oriented because isn't usual to have version bumps in updates.
So pick your gnome-packagekit or zypper up to get the latest GNOME update.

The news on openSUSE GNOME don't end here... i submitted a request today for gnome-color-manager, shared-color-profiles, libgee and tracker to be included on the main distro so expect these packages for 11.3 and GNOME:Factory/GNOME:Apps really soon.
The team also have GNOME 2.29.5 updated on GNOME:Factory repository including the latest zeitgeist and gnome-shell in case you want to test/develop/enjoy GNOME 3.
If you want a new package on openSUSE GNOME add it to the wishlist and i can take it (at least until i get a job :) )

With this good stuff it's also an important time to try openSUSE, join the team and have fun!

PS: Thanks to Magnus and Dominique for their work on this update

the avatar of Carlos Gonçalves

PySide packages for openSUSE, Mandriva and Fedora


As some are already aware of, I've been packaging PySide (including apiextractor, generatorrunner, and boostpythongenerator) for openSUSE since the project has been publicly announced.

Not only stable/released versions have been packaged, but also snapshots taken from mainline git repository with both built and hosted on the openSUSE Build Service in my home dir there (home:cgoncalves:pyside and home:cgoncalves:pyside:devel).

Yesterday I took some time updating the snapshots (ie. home:cgoncalves:pyside:devel) to now build against shiboken instead of the not-yet former boostpythongenerator. Apiextractor, generatorrunner and shiboken built successfully, while PySide did not because I've tried to build it with Qt 4.6 but due to bug #124 it failed, and in the meantime I've switched it back to Qt 4.5.

Moreover, I'm expanding this packaging work to other distributions namely Fedora 11, Fedora 12, Mandriva 2009.1, and Mandriva 2010 sharing the same specfile with openSUSE 11.1, openSUSE 11.2, and openSUSE Factory that already live there for quite some time.

Everything have been built okay for these distributions, except on Mandriva 2009.1 and openSUSE 11.1 where PySide (only) is failing (older gcc version version issues I suppose) and on Fedora 11 i586 and openSUSE 11.2 i586 with PySide failing, too, but due to bug #111

So, in case you are interested in testing these non-openSUSE packages, which I didn't I may add, please do so and report back to me whether they are okayish or not.

Finally, keep in mind that for now I'm only referring to repository home:cgoncalves:pyside:devel (snapshots) and not to stable versions. Plus, you won't get yet a full featured Python bindings for Qt since the PySide team is under heavy work on completing the QtCore module first with Shiboken before moving forward to other modules.

Please refer to [PySide] PySide packages for openSUSE, Mandriva and Fedora for further discussion.
the avatar of Katarina Machalkova

On testing

( I promised this article to Lukáš  today, so now I really have to write it :) )

What is the most important part of software project? Experienced developers? Creative user interface designers? Good managers? Meticulous testers? Decision making in the right hands? Hmmm ... if you ask me, it's balanced combination of all of these, but this is not what I'm going to write about. Testing - that's (maybe along with l10n work) one of the most underestimated and largely invisible part of any software project, be it a small appliance or something as large-scale as Linux distribution.

Hackers often look down on QA guys and view them as those not being smart enough to actually write the code. Nothing can be further from the truth. A good tester is worth his/her weight in gold. Fairly recent experience with work on (partially closed-source) project taught me a lesson about vital importance of  testing that I'll never forget. Really. Even the best code is dead without somebody testing it.

It is a tester who has to, using his/her experience and intuition, be able to pinpoint weak points of the software. When implementing a feature or creating a bugfix, developer's time is just enough to do some basic testing, verify it works, the bug is really fixed and be done with it. Tester has to use his/her creativity and come up with scenarios developer never dreamed about.

Tester has to have enough patience to go through the same boring set of basic routines with each and every new build. His/her learning curve with a new software has to be pretty steep. In limited time, s/he has to understand principles and configuration of the software and start using it as if s/he was an advanced user. At the same time, s/he has to quickly find out where the borderline between PEBCAK (Problem Exists Between Chair And Keyboard aka Layer 8 issue) and a real bug lies. I have to admit that this was the reason why I pretty much sucked at testing - I was so anxious about "I don't want to look stupid and file an invalid bug" that I spent hours and days studying docs and verifying it's not just me doing something wrong. I didn't realize that misleading documentation or confusing UI qualify as bugs as well.

When the project is finished, hackers are the guys in the spotlight and, sadly enough, QA work often stays unnoticed. Worse even, if the whole thing is a failure, testing squad is the first one to blame ("Damn, those guys must've had no QA. What? They had some? What they have been doing all that time then?"). Needless to say, that doesn't exactly boost one's confidence in the meaningfulness of his/her work.

To conclude, I'd like to dedicate this post to all our Four-Letter-Project testers (especially to the most active one of them) and to all former, present and future openSUSE testers. Ladies and gentlemen, a big round of applause for all those heroes, known and unknown!

a silhouette of a person's head and shoulders, used as a default avatar

hmm

Fall happened, Winter started happening, Snow fell and thawed, Christmas came and went,
New year came and went.

Oh, and I became godfather to my niece 2 weeks ago.

Nothing much more interesting to see here, move along.

a silhouette of a person's head and shoulders, used as a default avatar

My ZFS Home NAS/HTPC Box Build

I was looking to build a NAS (Network Attached Storage) to store all my music, photos, files, e-books and important work related files. I also wanted to have a central place for my backups and to be used sometimes as HTPC. So, a "two in one" solution (NAS and HTPC).

Even if there are many ready-to-go NAS solutions I decided to build myself one and having the HTPC on the same machine. Here is mainly what I wanted:

  • low powered system (64-bit microprocessor)
  • used as a media server (stream movies/music)
  • to be used sometimes as a HTPC, so I wanted HDMI (for HD video)
  • ZFS file system with all its goodies
  • gigabit ethernet interface to take advantage of the network bandwidth
  • nice chassis with four hot-swappable 3.5" SATA HDD (I am using just two HDD right now because the motherboard has only 3 SATA)

My NAS/HTPC specs are here:

home_server1es34069

I choosed FreeBSD as operating system, because I am more familiar with it than with Solaris. I recompiled mplayer with vdpau support (for HD video).

Here are the steps:

  • download the latest mplayer snapshot from their website
  • download these two files (ftp://download.nvidia.com/XFree86/vdpau/include/vdpau/) and put them in /usr/include/vdpau (create that directory)
  • ./configure --disable-x264-lavc --disable-x264 -–enable-vdpau
  • gmake
  • gmake install
  • check to see if you have vdpau support with: "mplayer -vo help". If you see something like: "vdpau VDPAU with X11" then everything is ok.

Some additional steps/configs:

  • add zfs_enable="YES" in /etc/rc.conf
  • add  the following in /boot/loader.conf:
vm.kmem_size_max="1024M"
vm.kmem_size="1024M"
vfs.zfs.arc_max="100M"
  • zpool create storage mirror ad4 ad10
  • zfs create storage/archives
  • zfs create storage/backups
  • install samba, duplicity, rsnapshots, rsync, unison, ushare, ...

Right now, everything is working very well, I am very happy with the setup, but I still didn't manage to have sound over HDMI, so, a temporary solution will be to connect an additional speaker system to it.

I don't need any fancy remote control, I have a logitech wifi keyboard/mouse, because I like to be able to read the news in the morning (during cofee time) using google reader

The total power consumption is about 35W idle / 45W load which is pretty good, I think.