Some week ago, I’ve stumbled upon a very promising font project. It’s called the Exo Typeface Family and I think this could be a valuable addition to our distribution:
(more…)
Archive for the ‘Usability’ Category
The Exo Typeface Family
December 8th, 2011 by Thomas SchraitleNew Style for YaST2
October 24th, 2011 by Thomas GöttlicherYaST2 got a lot of improvements which will be available in openSUSE 12.1. YaST doesn’t accidentally overwrite configuration files anymore (last bug fixed
) and snapper provides a rollback function for configuration options, just to mention a few. Therefore it’s time to give YaST2 a new and fresh style. As YaST Qt supports Stylesheets it’s simple to influence YaST’s style.

FACTORY contains the new style already. Packages for older releases are also available in my build service project: http://software.opensuse.org/download.html?project=home:tgoettlicher:Factory&package=branding-openSUSE.
I hope you like it. You can use YaST’s Stylesheet Editor to play around the the stylesheet as described in my this blog post. Please send me improvements you want to share. Thanks.
Unity 2D to enter GNOME:Ayatana soon…
May 19th, 2011 by Nelson MarquesIn the past days I’ve been packaging and fixing some issues on Unity 2D for inclusion on the GNOME:Ayatana repository in the openSUSE Build Service.
This gave me an excellent opportunity to test a few components share by both, Unity and Unity 2D, which is the case of ‘unity-place-applications’ and ‘unity-place-files’, both using Zeitgeist which is already in Factory for the upcoming openSUSE 12.1. We thank the integration of this packages to Federico Quintero. Thanks Fred.
A few more additional packages need some care and once they get updated and tested they will be uploaded to GNOME:Ayatana, at which time I will provide an installer (1-Click) for those willing to test Unity-2D. Unity 2D will be the first application to use the indicators I have prepared in the past which all all found working, except 1, the AppMenu (strangely it works on GNOME2 panel without issues).
This is how Unity 2D looks like. There are transparencies because I enabled ‘composite’ on metacity, which works very nicely. As far as I could understand, the developers of Unity 2D are also looking into implementing Compiz with Unity 2D, which would be sweet.
Unity introduces the ‘dash’ which is pretty much the following screen. Transparencies are enabled (though metacity composite) and the notification bubble belongs to NotifyOSD (already present in openSUSE 11.4 as optional). This is one of the three issues I have to fix, the icons displayed on the dash should have text underneath, it’s not showing. The top icons are quick links to Program Categories and the ones bellow are the default applications which are setup in GNOME.
The launcher panel on the side auto-hides, and seems to be working. The three icons displayed in last are respectively: Workspace selector, applications menu and files. Everything seems to be working with them, and the 2 last are components shared with Unity, and they both rely on Zeitgeist. Here’s a few captures of what they do…
There’s also a feature from Unity which is cute… The title artifact of the decorator window (metacity, which required a few patches) is removed and implemented on the top bar when the window is maximized. Sadly for me the AppMenu (menu proxy) isn’t working properly, this is another thing that needs fixing…
This should cover pretty much the functionality that is available currently. There’s a few issues still remaining before I can push this to GNOME:Ayatana:
- I tried not to have the need to patch gnome-session, but since Unity relies on the Session Indicator to have this functionality, gnome-session will need to be patched (should be ok, because it also requires the backport patch for defining –sessions for openSUSE 11.4).
- Unity 2D itself relies on a few gconf hacks that should be on a schema file. I’ve talked to upstream and this is planned already, so once it’s release, that’s when it will be published.
- There’s one issue also with backgrounds and workspace switcher… unfortunatly the workspace switcher only renders wallpapers if they are in image format (no .xml stuff), so this can turn some wallpapers not to render, which eventually ends up in the background of the switcher being the one defined in GNOME as solid color.
So the order of TODO’s for GNOME:Ayatana is pretty much this one:
1. Implement dependencies and then Unity 2D;
2. Make sure Compiz is well implemented, because Unity will require Compiz at it’s best shape;
3. Make sure nux and other twisted dependencies are properly implemented;
4. Implement Unity itself;
This are the latest news for GNOME:Ayatana…
Where our bugzilla needs improvement
April 15th, 2011 by Bernhard Wiedemannupdate 2012-02-07: Success: after bnc#732504 you can now open Advanced Search and find RESOLVED/DUPLICATE bugs by default. When bugs are finally solved and fixes released, those can then be moved to CLOSED state to no more appear in search results.
bugzilla.novell.com aka bnc is the central tool to track bugs of openSUSE.
It has a guided bug submission form that helps & encourages reporters to search for existing reports on an issue.
However, the integrated search function only shows open bugs. In principle that is nice, but bugs marked as duplicates of open bugs do not count as open. Also it is common that developers mark a bug as RESOLVED/FIXED as soon as they uploaded a patch into the OBS devel-project. Such a patch then needs some days until it gets into Factory or the Update repos where normal users would benefit from the fix. During that time, there will still be people with all regular updates installed hitting the bug and not finding it on bugzilla because it is no more marked open. Of course, one could also search for RESOLVED bugs, but this brings up a huge list of issues that are long solved, but never were marked CLOSED (e.g. openSUSE-11.3 has 453 CLOSED vs 2727 RESOLVED).
This wastes time of reporters writing a duplicate bug-report and wastes time of developers having to figure out that it really is a dup. This is probably why other projects recommend setting bugs to ASSIGNED/FIXED until the patch is released. Unfortunately bnc lacks this state.
Also bugzilla has an UNCONFIRMED state for new bugs that need triaging to get into the NEW state (named “Reproducible but not assigned” in other projects). Such a state is unavailable on bnc, so that people can not tell apart bugs that have been forgotten from bugs that are known to exist, but just wait for a developer to fix.
There was also little integration between OBS and bnc. I have therefore written scripts to update bugzilla entries with links to submit requests on OBS mentioning e.g. bnc#685133 (<=see link for how it looks like). But it still could be made a lot more useful.
Overall, there is some room for improvement to make people’s lives easier, and allow us having a lot of fun…
eGalax touchscreen on CTFTAB how to make it work
December 8th, 2010 by TuukkaI’ve been playing with CTFTAB and was trying to make touch screen work on openSUSE 11.3. First everything went easy but then troubles arised!
(more…)
BugDay
November 22nd, 2010 by Alexander NaumovAt the last openSUSE project meeting and after the discussion about “zombie” bugs on the opensuse-project mailing list, a small team of volunteers agreed to organize a Bug Day on Saturday, November 27th. What is a Bug Day? This is a day when many people from the community help to triage bugs in Bugzilla. It is a good and easy way to get involved in the openSUSE project!
Here is what you need to participate:
– a recent version of openSUSE (11.3 or a milestone of 11.4). It’s okay to run openSUSE in a virtual machine.
– an IRC client to interact with the other participants
– good mood
A small team will organize the event by providing lists of bugs, and will be available to guide new contributors if needed. So it will be easy to help!
For this specific Bug Day, we will focus on the “zombie” bug reports: those are reports against old versions of openSUSE (openSUSE 10.x and 11.0). As some reports might still be valid, we don’t want to close all of them automatically. We will therefore check all those reports to see if they are still valid in the latest version of openSUSE (11.3 or a milestone of 11.4). The goal is to close those bug reports if possible, or, if they are still valid, to move them to a current version of openSUSE so that they’re not lost in limbo. So during a full day, people come on irc and help each other triage bugs.
Please note that this is only for openSUSE bugs (living in bugzilla.novell.com), but a solution for some bugs might be to forward them upstream.
Come on #opensuse-bug (freenode) on a Saturday 27.11.2010, we’ll be glad to have you join the fun!
RTFM!
October 23rd, 2010 by Thomas SchraitleBefore and during the openSUSE conference, some nice people (Jens-Daniel, Jürgen, Darix) created the following site for you:
http://rtfm.opensuse.org http://doc.opensuse.org
Thank you guys! I like the thrilling name.
It’s a static page (at the moment?) and collects the current documentation from several products and projects. Probably you will see more to come in the next weeks.
Have fun!
Update (AJ since Thomas is ill) 2010-10-27: Based on the feedback received, we’re going to change now rtfm.opensuse.org to docs.opensuse.org. So, you can reach the fine side under http://docs.opensuse.org and http://doc.opensuse.org.
Documentation
October 13th, 2010 by Alexander NaumovHi folks,
this post is just request for all obs-packagers. Please, don’t forget write some documentation about your projects (which you maintain or develop). I mean, documentation for developers. This make more easy to understand logic of program, connection between some modules inside or interfaces between widget/applet and “system/hardware part”. For sure, comments in source code (or in changelog) help, but some times they give not so much clarity.
This is not so complicated to write one-two pages about project, which you hack. This also can save time of new developers. They will not ask you about architecture of project, and that will save your time too
I don’t know how will be better to do it: use wiki (create a new page) or add just text-file in source project. Anyway it’s not so important where will be this documentation, main things that this documentation will be exist
Adventures with Intel Atom D510 board
October 8th, 2010 by Togan MuftuogluFor long I had been using my old laptop for everything; building images with KIWI, writing documents using LaTeX and Docbook XML, sorting my photos with Digikam. I have been upgrading since version 9.0 and at the moment opensuse 11.1 was the release ( OK with lots of new software thanks to the Build server. However, for some odd reason I wanted to have something new. Dangerous word, new is.
I have 2 Intel Atom’s running for my mail and web servers and I was quite happy with their performances, (by the way I am still happy). Hence I decided to ride the change train and bought the Intel D510 board
opensuse 11.3 Kde LiveCd worked fine and using Susestudio I designed my image. So far was really good. Booting the usb brought my feet back to earth. A frozen screen. So I tried the failsafe option and I had a 800X600 display. Reboot and this time trying “nomodeset” option same thing. Nevertheless I decided to give it a go ( I can always use it at run level 3).
Last night I have decided to include the Kernel:HEAD repo so I am using kernel-default-2.6.36-rc6.25.1.x86_64 along with the X11:XOrg repos using X.Org 1.9.0.901 (1.9.1 RC 1) so now I have “1366×768 (the max my monitor can give) and I do not need to set “nomodeset” in the boot options anymore.
I have not tweaked everything yet, like my Logitech keyboard’s multimedia keys are useless in KDE at the moment. At the end they will work one way or the other, I am sure.
Lesson Learned: do your homework well before jumping the change train or enjoy the adventures
Free BEER for free people
September 17th, 2010 by Alexander Naumov
When we call beer “free”, we mean that it respects the users’ essential freedoms: the freedom to drink it, to study and change it, and to return empties with or without some changes. This is a matter of freedom, not price, so think of “free speech”… but in this case also “free beer” too.
Why man have to choose a free beer? Because it’s open and free to use. Everybody can give some feedback on the freebeer’s twitter page.
The project was started by Wädi Bräu in Switzerland like “open source beer” project. On the home page you can get more information about this project, for example, news and last updates.
License: creative commons.
Alcogol vol: 4.8 %
Size: 0.33 L
Be free… drink free beer
p.s. Who know, maybe Novell will be sponsored this great open source project (?)





