Home Home
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

Author Archive

Unity on openSUSE: UPDATE

January 30th, 2011 by

Unity works as a plugin for Compiz using the glib mainloop. Currently the development version of Compiz available in OBS X11:Compiz already provides this requirement (glib mainloop) as a plugin. This version and two git snapshots I’ve builded were crashing heavilly, so I’ve decided to take  a closer look into Ubuntu’s packages and build from their sources on my devel project. This has proven wise as their snapshots (2010-11-25) with their patches removed the crashes on compiz.

The patches applied include the new unity-window-decorator which works fine. Here’s a small screenshot of GNOME’s System Monitor using Unity’s window decorator (which relies on a patch on metacity to enable UX Shadows).

The theme for this screenshot is Ambiance (also from Ubuntu) with a changed color scheme. This shot was taken on M6 with the newest FireGL drivers from ATI. I’ve noticed some changes on the blur effects on this driver, but I really can’t develop much.

I haven’t seen crashes on individual components when I test them (ex: unity-panel-service and unity-window-decorator), which seems to be a good pointer.

Currently I’m working out in porting the Unity wrapper and some scripts from Ubuntu to the reality on openSUSE as many files seem to be distributed on the filesystem in very different places. Just to name an example… compiz on openSUSE currently stores it’s profiles and stuff on $HOME/.config/compiz-1, and Unity is searching those files on $HOME/.compiz-1, and as such, fails to find them. This is where I’m currently placing my efforts. This should fix soon the ‘unity’ wrapper.

To make this short… Compiz isn’t crashing anymore or seg faulting, and Unity is picking up the information required from different file locations on the file system. Once fixed, we should have a running Unity for BETA soon.

My very special thanks to Malcolm Lewis for making the integration of Unity with Compiz possible in a very nice way and for fixing many bugs that allowed us to successfully build this packages.

As soon as we have more developments, those will be posted.

A heartly ‘Thank You’

January 27th, 2011 by

I would like to leave a very fond ‘Thank You’ to everyone who has placed their trust in me on the recent elections. The number of votes on me was a true surprise.

This election was probably one of the most important in openSUSE history, mainly to the fact that it’s the Board that is going to push the Foundation forward. I find the results very pleasing and I’m happy to see Henne and Peter moving up to help on those efforts.

Thank you all for an inspiring source of motivation.

Nelson

Unity, Compiz and ATI…

January 22nd, 2011 by

I’ve finally added the Compiz packages to my development repository and unity itself alongside with some tools.

There are several bug reports on launchpad concerning ATI users, involving RADEON DRM driver and FireGL (fglrx) drivers. Unfortunately for me, I’m also a very happy ATI customer.

I’ve struggled yesterday with some ABI problems on compiz, this was mainly because I had git snapshots from different days, and updating and rebuilding it, really solved the issue.

Today I’ll be implementing the required patches for compiz by Ubuntu,, and hopefully this will enable me to test Unity, this time on a spare laptop with Intel Graphics chipset. I was hoping to pop some screenshots today, unfortunately, I’m having a couple of problems with Compiz that hopefully a couple of missing patches will solve.

I’ve left behind the ‘clutk’ package, as it’s currently broken and I need to take closer look into ‘glew’ and work it out. Something for monday/tuesday spare time.

For the time being, the only screenshot I have to show is the one of CCSM (compizconfig-settings-manager) with the Unity plugin.

Massive update on Ubuntu software…

January 20th, 2011 by

Screenshot using Radiance Light Theme and default Ubuntu indicator layout.

Some brief updates about the ongoing work towards bringing Ayatana Project software into openSUSE:

1. Software Updates

Canonical recently released a batch of updates which bring new functionality (Indicators seem to respond faster now) and very nice improvements, some of them contributed by down-streamers. From my humble experience I would risk to claim that Canonical is doing an excellent job as an upstreamer. I’ve updated all packages to the latest versions. This allowed to remove some patches.

2. Unity

Unity is now one step closer. For Unity I’ve started to package Compiz git snapshots from the correct branches pointed by Unity documentation. This brought something new to me, cmake. I’ve done this very slowly, reading some docs meanwhile about cmake. My packaging around Compiz is mainly based on OBS X11:Compiz repository, so pretty much all the credits should be for the original project Packagers which done an awesome job. Currently I’m missing only 3 packages to test Unity. Recently with kernel and mesa updates some issues around ATI hardware seem to have fixed for openSUSE Factory users, which enabled in my case FireGL, therefore I can test properly Unity now and check for the integration into openSUSE.

Unity by default uses the Ayatana’s Indicators, and if they are not present, it will fallback to GNOME’s applets. This is very nice and I’m thankful Canonical made it this way. This brings non-Ubuntu users the Unity experience at almost no trouble, since there isn’t actually much patching required to implement Unity.

3. GNOME:Ayatana Repository

GNOME:Ayatana Repository will be populated during the next two weeks with the latest changes and will provide for the time being the Ayatana’s Indicators and Unity. I am currently working around libappindicator stack and it’s Indicators. Currently I’m testing the patches required on the GTK+ stack and this is pretty much the last barrier before going into #STAGE2, polishing and populating GNOME:Ayatana.

It’s not decided yet what packages are going to present on Factory. My wish is to push only Unity into Factory and it’s dependencies, this might not happen for 11.4 as I’m not sure about the freeze schedules and it might be too late already, but since we’re depending on Compiz upstream, we’ll see what happens. Even if Unity isn’t going to be available on Factory, I’m sure we can use KIWI or SUSE Studio to release a small openSUSE Unity Spin.

I’ve also decided that I (typo: previously would) wouldn’t like to see Unity available by openSUSE before the official release from Ubuntu, for which I wish all the success.

Since the very early start that I’ve been using pkg-config as much as I can. According to some information that I collected previously, this would be great for cross-distribution build. Depending on the time and work done, I might make the necessary modifications and enable cross-distribution building on this project, thus, making it available for other RPM distributions supported by OBS. This will require a bit of testing before, so it will be work to be done after 11.4 is released and during it’s lifecycle. Maybe by the time of openSUSE 12 gets released, we will have this project also available for other RPM based distributions. I have no knowledge on Debian packaging, but Ubuntu ships this software and Debian probably has it also available so… that won’t be a problem.

4. Artwork

I am providing on GNOME:Ayatana Ubuntu’s Light Themes (Ambiance and Radiance) and offering a patched version of Metacity that renders those themes perfectly. I’m not changing the original colors from the themes or modifying them in any way. So they might be a bit more of orange and not green.

I’ve contacted some people to ask if they would be willing to donate some artwork to make a small package with Wallpapers, some have answered yes, so I will make a small package with a couple of wallpapers for the traditional resolutions and distribute it alongside with this software as optional as always.

5. GTK2, GTK3 and QT

Implementation of GTK3 will be done within the next days, as I am also considering enabling QT support for KDE users (Indicators only for now).

That’s pretty much the result of the last days of work… more news to come in the nearby future.

A brief update…

January 17th, 2011 by

In the last days I’ve been leaving my full attention to Compiz and the famous glib main loop. I’ve made a small perl script to compare my local builds with the ones available on launchpad… nothing too fancy, but it seems to work. During the last days Canonical updated a lot of software.

I’ve decided to start updating the on my test repository to the newer versions. A couple of new packages are required as dependencies (the most impressive one is utouch-evemu, which is a part of Canonical’s Multitouch uTouch stack).

The number of updates is quite impressive, the number of patches (even on some new updates) is equally impressive… I’ve just realized that GTK+-2.0 has been subjected of a couple of fun patches and gobject-introspection is becoming mind crushing… Either way, the work continues, and unfortunately for me I was planning to do a small open beta phase for Factory users soon… but all this changes will require much more work and a lot of packages will have dependency lists updated.

The next days free time will be spent around this massive update, I am sure it will pay off. If anyone is using my test repository on my home project, expect some turbulence during the next days. Since I’m on this, I’m already starting to enable GTK3 wherever I can do it in a safe way, nevertheless, it’s just to speed work for the time being, as much things are changing.

Questions for Board Applicants

January 17th, 2011 by

Today I’ve decided to send a couple of questions for Board candidates. To me it is important the answer to this questions, as through such answer it will be possible for me to sharp my opinion about some of the people behind the applications.

The questions aren’t all direct and involve a critical analysis of quotations provided. The thread can be visited on the openSUSE Project mailing list.

I’ve used quotations from 5 different people that should be familiar to most people.

* F. Nietzsche – http://en.wikipedia.org/wiki/Friedrich_Nietzsche
* Adam Smith – http://en.wikipedia.org/wiki/Adam_Smith
* Daniel J. Bernstein – http://en.wikipedia.org/wiki/Daniel_J._Bernstein
* Richard M. Stallman – http://en.wikipedia.org/wiki/Richard_Stallman
* Mahatma Gandhi – http://en.wikipedia.org/wiki/Mohandas_Karamchand_Gandhi

openSUSE Factory: ATI FireGL 10.12

January 13th, 2011 by

I’ve had some problems in the past with openSUSE Factory and ATI support… even the normal radeon driver wasn’t worked properly. After the last updates, the radeon driver started working properly and I’ve decided to install the ATI FireGL driver which is actually something I need to continue testing and debug Unity implementation on openSUSE.

IT WORKS!

Here’s what you need (64 bit users):

* Install the required dependencies to compile the kernel module (currently on 2.6.37-rc5-12-desktop). 64bit users will require the following:
[code] zypper in kernel-source compat-32bit qt3-32bit libstdc++ libgcc xorg-x11-libs-32bit xorg-x11-devel-32bit Mesa-devel-32bit fontconfig-32bit expat-32bit freetype2-32bit zlib-32bit gcc make[/code].

* Download ATI FireGL driver (version 10.12) from ATI website (http://ati.amd.com).

* Extract the files using the command:
[code]sh ati-driver-installer-10-12-x86.x86_64.run –extract[/code]
This will create a small folder which starts with fglrx*. Change directory into that folder…

* Download the following patches:
sema_init.patch
–  fglrx-2.6.36.patch
–  makefile_compat.patch

* Apply the patches (patch -p1 < file.patch).

* Run the following command:
[code]sh ati-installer.sh  8.801 –install[/code]

* Follow the installer instructions. Finally check /usr/share/ati/fglrx-install.log to check if everything is cool…

* Restart using your favorite method… mine is ‘shutdown now -frn’.

Enjoy FireGL on openSUSE Factory!

Wallpaper Community Pack #1

January 13th, 2011 by

I’ve received some emails and some positive feedback about one wallpaper I used for a couple of screenshot’s I’ve used in the past, including also information requests about where that very same wallpaper could be found. I’m happy people liked my choice.

The wallpaper is question is the following, which can be found at gnome-look [dot] org:

Green Snake HD - by Kmurat @ gnome-art.org

It is clear to me at this stage that Artwork has good demand and it’s a ‘value +’ recognized by many users. Understanding this, I’ve decided two things:

* GNOME:Ayatana will have a small Artwork Package by the Community, I’m currently contacting Kmurat to check if he can change the licence on this artwork piece (with over 20.000 downloads on gnome-art) so I can use it for distribution. Currently it’s licensed as CC BY-NC-ND, in which the NC can be probably a problem. Let’s wait a couple of days and see… Either way for those who asked for the source of this wallpaper, click on the image above.

* I will create a small package with wallpapers from the community and make it available (for GNOME, KDE, etc) users.

My intentions are to include a set of wallpapers (4/3, 16/9 and 16/10) of around 5/7 wallpapers from several artists and community contributors. The first person I’ve contacted regarding this was Javier Llorente, a openSUSE Artwork Team and KDE contributor, which donated and pointed some artwork. I’ve also sent a small email to María ‘Tatica’ Leandro, a contributor of Fedora Design Team from South America asking if she had something that she could share with us for this community package (I did loved some of her submissions into Fedora Art). Additionally, I’m also going to nag Sirko Kemter (gnokii) for a contribution…

Once this is assembled (already have 5 wallpapers) I’m going to package it, run a sanity check and prepare it for distribution…

UPDATE: María ‘Tatica’ Leandro has answered positive to my email requesting for a donation, Sirko Kemter also answered positive.

The first days of 2011…

January 11th, 2011 by

José Morinho - Best Coach of the World, FIFA 2011, a warrior of Portugal!

I’ve been away for a couple of days due to a small increase work load from the University and the exams are somehow nearby.

Regarding openSUSE, I’ve builded already Compiz with the ‘glib main loop patch’, fixing some other minor issues on plugins packages, and still waiting on development on other stuff that might be interesting.

It’s time now to prepare the last packages for a mass upload into GNOME:Ayatana which should happen soon. I’ve also going to book some time in the next GNOME Team meeting to gather some information about the best way to do this.

I’m also happy that a couple of people jumped in and helped in the TODO tasks, this is the case of openSUSE contributor Malcolm Lewis.

This is just a small update on whats happening on Nelson’s land, as my private battalion of ‘twisted monkeys’ knows no rest. Now it’s time to scribe a couple of emails….

PS: I couldn’t forget to leave a public statement regarding the ‘Mister’ José Morinho, which wrote another glorious page for every Portuguese! More than a coach, not just a man, a warrior of Portugal!.

openSUSE Board: about my application…

January 4th, 2011 by

Dear all,

I’ve decided to submit an application to the openSUSE Board. As a part of the procedures, there is the need of also complying with having a user page and provide some interesting information (openSUSE Elections Platform Template). This post should fulfill those requirements and provide a bit more of information about this sudden move.

Introduction and Biography

My name is Nelson, and hopefully I’m just another face in the crowd. I am a Linux enthusiast and once a believer that Linux could effectively replace other systems, even on the Desktop. I see myself as a end-user, as I don’t have too much demanding computing needs, for the most I use my computer just like any of the traditional end users out there. I don’t have a featured list of accolades or victory knots on my belt, instead I have a random casual action on a distant past on the national scene…

I’ve started my Linux experience with SuSE Linux 5.2 and kept going till SuSE Linux 7.1. I ended up by swapping to Red Hat and later to Fedora. I’ve return to openSUSE as it became more attractive due to FireGL support. It was a friendly transition and openSUSE tools helped a lot.

Major Concerns (previously ‘issues’)

* Secure a stronger position amongst the Desktop. Linux Desktop isn’t dead, neither emerging consumer electronics markets are a risk to the Linux Desktop. Nothing will change in the next 5 years. Take my word for it.

* Secure stronger distribution channels, expand the media partners network and optimize current channels for massive deployment of contents.

* More updates on people’s work through the planet. The press is keeping an eye on it. People should have the motivation to post more often, thus providing the media partners and our news team with more contents. Our userbase will see a non-stopping community, always working for the ultimate goal of satisfying their needs.

* Start implementing a structure that allows openSUSE as a Community to be managed as a service. Deploy extensive marketing to our established community and educate them on the basics of service marketing and customer loyalty builds. Our future depends greatly on this.

* Extend and improve the cooperation between openSUSE and other projects (ex: GNOME Project, KDE, others). There exist countless ways of doing this.

* Build and promote a openSUSE Desktop experience! This means deployment of more optional software, deployment of artwork by the community and of features voted by users.

* MOST IMPORTANT OF ALL: we need to DARE for more. We need to take risks and battle for our choices. Being conservative or follower doesn’t help. We need a strong vertical strategy.

Minor Issues

World Domination.

Role of the board

The role of the Board from my perspective is to be the Guardian and Sake keeper of the openSUSE values! The Board should also be the keeper of strategical guidance and the big pusher of the Community. From my perspective the board should enforce all necessary policies to ensure that the Community expands in numbers and contributions, but also keeping the orientation that allows us as a community to reach the strategical objectives defined previously.

The Board should also play a ‘self assessment’ role on the community and take swift and hasty action whenever required. All users should face the openSUSE board as a ‘beacon of light’ showing the way to the commity!

Why you should vote for me?

For all the subjects I’ve pointed as important to the future, you will notice that most of them can’t be enforced by the Board or by a group of persons. They need to be a free initiative from everyone around openSUSE. Not because we demand it, but because you understand the benefits that the community as a whole can take from such actions.

Aims/Goals

* Extend the list of official media partners and create a stronger and wider diffusion network for our contents, thus promoting existing sub-projects like News.

* Promote actively the participation of openSUSE contributors on the Planet. We need to update more often what we’re doing. The press is around, feel free to provide them the contents they need, thus you are promoting also openSUSE.

* Promote a stronger marketing commitment towards the established community! We need this!

* Survey often and a lot our community. Be always aware of our users needs and requirements so we can be ready to answer them.

* Make better usage of current materials and deployment capabilities. A quick example, YaST’s installer has some slideshows… We can improve those as a promotion method for upstream strategical projects, openSUSE and Community.

* Self assessment of all the resources currently available. We need to have a goal and methodology to allows to take quick action when required and provide accurate data that can influence our future.

* Promote more community efforts in the Desktop area. For example, community artwork packages, artwork repositories… etc.

* Ambassadors program requires methodology for self assessment and diagnose of ‘investment vs returns’. We can’t just ‘give’, we need to take something in return as well. What do we want in return ?