Now that 11.2 gets closer and closer to the rc status being able to play mp3 becomes important in order to make the testing experience even nicer.

Here is my workaround to get that mp3 working in amarok. I do not know about the dvd’s as the only one that I own is to boring to use it for testing purposes

wget http://download.opensuse.org/distribution/11.1/repo/oss/suse/x86_64/libcdio7-0.80-5.30.x86_64.rpm
zypper in file:<Path-to>libcdio7-0.80-5.30.x86_64.rpm
wget http://download.opensuse.org/distribution/11.1/repo/oss/suse/x86_64/libiso9660-5-0.80-5.30.x86_64.rpm
zypper in file:<Path-to>libiso9660-5-0.80-5.30.x86_64.rpm
wget http://download.opensuse.org/distribution/11.1/repo/oss/suse/x86_64/libMagickCore1-6.4.3.6-5.3.x86_64.rpm
zypper in file:<Path-to>libMagickCore1-6.4.3.6-5.3.x86_64.rpm
wget http://download.opensuse.org/distribution/11.1/repo/oss/suse/x86_64/libMagickWand1-6.4.3.6-5.3.x86_64.rpm
zypper in file:<Path-to>libMagickWand1-6.4.3.6-5.3.x86_64.rpm
zypper in libxine1-codecs

So as you can see I just use the missing libs from 11.1.Of course I assumed that you added the 11.1 packman to your repos already.

Ladies and Gents,
we’re glad to announce that SOAD Linux 3.2.1 is out and available for download.

This is a bugfix release mostly. Please read the changelog:
Changelog

Active mirrors are updated weekly, starting from Monday:
GWDG.DE
Yandex.ru

We do need your feedback about “Ecomorph” – some kind of auto configuration script is already managed (no manual adjustments are required before launch), but looks like some important parameters/values are still missed unfortunately. Already collected several “White Screen Compiz Bug” reports from owners of NVIDIA GPU’s and just wish to collect some more to get the reason how to improve it. Right now (for LiveCD/LiveUSB) “Ecomorph” should work with the modern NVIDIA (drivers already in) and with other video cards, where “Compiz” is supported by a current “Mesa”/(current Xorg drivers). The case here is to tweak some values to be sure that things could work “out from the box”.
Example: if we’re building/installing NVIDIA drivers manually from official *.run.sh – everything is just fine. If we’re using the “packaged” rpm’s with the same drivers – “White Screen” could happen with “Ecomorph”.

As a sweet eye-candy the work for “Restoration of a GANT iconset” has been started – hope you like it. Current status – a bit more then Alpha, works, but feedback is highly appreciated.

Soon we’re planning to update our Enlightenment repositories up to the current E-svn. QA is in progress. Unfortunately bleeding-edje svn code is not always stable enough :).

Regards,
sda

Our call to apply for the openSUSE Core Test Team end of July attract a great deal of attention. So we got applications from nearly 50 members out of the openSUSE community, much more than expected.

Caused by that large number of offers to move testing of openSUSE forward, we decided to increase the number of members for the new openSUSE Core Test Team from 15 to 25. A number that enables even more areas to be covered by the openSUSE Core Test Team.

Six weeks later – with the release of Milestone 7 of openSUSE 11.2 – the team is formed and already started his work to ensure that openSUSE will also be a rock-solid Linux distro in the future. First discussion about prioritizing tasks is already started and members of the team are planing their first real time meeting on IRC.

But everybody that is not (yet) part of the team is also able to take part in discussions of the openSUSE Core Test Team and contribute. The communication platform for the new team is the public opensuse-testing@opensuse.org mailing list (further information at http://en.opensuse.org/Testing). And of course you don’t have to be part of the Core Test Team to help the openSUSE project with testing of Milestone 7 and later releases (which are available at http://software.opensuse.org/developer).

I’m exited to see the team to carry the world before one.

Contributors Romain Tartière, Bertrand Lorentz, Robert Dyer, Andreu Correa Casablanca Features

• View Fullscreen option
• User docs translated into ca

Bugs Fixed

• Build fixes for *bsd
• Update recent files list after opening a document
• libdir expansion issue fixed in Hyena, depends on 0.2

Translations

• es (Andreu Correa Casablanca)
• pt (Filipe Gomes)
• sv (Daniel Nylander)

See the website for links to tarballs, git, packages, the mailing list, irc, bugzilla, and more. I'd like to thank Bertrand Lorentz for doing the actual release!

Last 3 weeks were spent with a week of vacation, a week of work, and another week of vacation.

First vacation week ... I went to the Linuxbierwanderung (Linux Beer Hike), this year happening in Helmbrechts, Upper Franconia, Bavaria, Germany. Nearly no Linux (except running on Laptops and in some smaller discussions), not much walking (for me personally no walks), but some sightseeing, and quite an amount of beer. Saw the German-German wall museum in Moedlareuth.

One week of busy work, including hurrying out another kernel fixing a new local root exploit.

And another week of vacation, this time going to Maurach at Achensee in Tirol, Austria with my best friend Bianca. Nice hotel with good food, wellness area and in easy distance from the lift. We spent two days walking in the mountain, one week of relaxing in the sea bath at the Achensee, and one day shopping in Innsbruck. Also took a ride with the local Steamrailroad. Nice and relaxing week, pictures here.

Recently lots of people asked me how to build QJson under Windows. Most of them reported build/link errors, so I decided to try personally.

The good news is that QJson can be successfully built under Window, I can show you proof ;)

{% img /images/qjson/qjson_windows_1.png %} {% img /images/qjson/qjson_windows_2.png %}

I have written the build instructions on QJson website: just take a look here.

One last note: if you have problems with QJson please subscribe to the developer mailing list and post a message.

We have started planning the sessions for the .NET/Mono Code Camp in Tarragona (Spain). The sessions are being organized in two tracks: a Mono track and an MSDN track. I plan to give at least a couple of talks: one about the upcoming release of MonoDevelop, and one about application extensibility based on Mono.Addins. If you are interested in giving a talk, it is now time let us know. You'll find here a form you can use to submit your proposal. We will select the proposals we find more interesting, and we plan to pay the travel expenses for all speakers. Update: sessions are going to be held in spanish. Update 2: we don't have a big budget, so we may not be able to pay full expenses to people coming from outside Spain. Update 3: the deadline for the call for papers is September 11th. I like how the Code Camp is shaping up so far. It will be a chance to meet with spanish Mono hackers and users, but it will also be a good chance to talk about Mono and Linux to an audience which typically is very Microsoft-centric.

I got to go tough installation routine again.
It is Radeon Xpress 200 graphic adapter that is making trouble.

The open source radeon driver is OK for almost anything, specially after removing strange sized "Virtual 3840x1200" when frame rates jumped to values comparable to proprietary fglrx, but the "Almost" is a keyword here.

Despite glxgears giving nice number of the frames per second, Google Earth was like molasses, and fan would start turning in high speed almost from start, YouTube videos refused to take full screen, with Flash actually going on strike.
So, to cover those cases I attempted to install fglrx again.

First attempt was to compile driver, but that didn't work well. The ati installer didn't do the job well.

Using /usr/share/ati/fglrx-uninstall.sh I removed remnants of "Hard Way" installation and used procedure described in http://en.opensuse.org/ATI_Radeon_Xpress


When all was done, Google Earth was running as it should, YouTube didn't complain to run in full screen mode.

Someone asked me if I could add the missing parts of GtkBuilder in Gtk#Beans so he could use it with IronPython on mono.

Hey, it looks there's no missing parts ! It all works fine since day one. Here's the the trick:

import clr
clr.AddReference('glib-sharp')
clr.AddReference('gtk-sharp')
clr.AddReference('gtk-sharp-beans')
import Gtk
import GLib
import GtkBeans
import System.IO

def PyBuilderAutoconnect(builder, target):
def _connect(builder, object, signal_name, handler_name, connect_object, flags):
    name = ''.join([frag.title() for frag in signal_name.split('_')])
    event = getattr(object, name)
    event += getattr(target, handler_name)

for object in builder.Objects:
    setattr(target, object.Name, object)
builder.ConnectSignalsFull (_connect)

class Application:
def __init__(self):
    builder = GtkBeans.Builder (System.IO.FileStream ('ui.ui', System.IO.FileMode.Open))
    #use this ctor if you don't like FileStream
    #builder = GtkBeans.Builder ()
    #builder.AddFromFile ('./ui.ui')

    PyBuilderAutoconnect (builder, self)
    self.window1.ShowAll ()

def onbuttonclicked(self, o, args):
    Gtk.Application.Quit()

Gtk.Application.Init ()
app = Application ()
Gtk.Application.Run ()

Now your IronPython skills are ready to rock Gnome3!