928 items (928 unread) in 19 feeds
Linux Mint Blog
(209 unread)
JJMacey
(84 unread)
Alberto Milone
(67 unread)
Linux Geeks United
(51 unread)
Линукс MINT (ru)
(46 unread)
Shane Joe Lazar
(26 unread)
Linux Mint Hispano
(120 unread)
Linux Manua (fr)
(38 unread)
Sourwire
(24 unread)
linuxmint-italia.org (it)
(18 unread)
linuxmint.m6blog.fr (fr)
(15 unread)
linuxmint.pl (pl)
(14 unread)
Mint Connection
(5 unread)
linuxmint-fr.org
(4 unread)
Videos
(55 unread)
Podcasts
(152 unread)
TLLTS (podcast)
(69 unread)
LAS (podcast)
(49 unread)
LugRadio (podcast)
(34 unread)
16:27
I have updated the NVIDIA driver 177.67 (still a beta) in Intrepid (a special thanks to Timo Aaltonen who sponsored the upload).
If you still have 2D performance issues, you can have a look at this post (a special thanks to nullack for suggesting this link).
NOTE: this driver won’t be available on Hardy until a final release of the driver is available.
19:36
If you experienced problems with the NVIDIA driver 173.14.09 you might want to give version 173.14.12 a try.
The driver is available on Hardy in the hardy-proposed repository (you will have to install it through EnvyNG, if you haven’t already done so) and should now work with Xen kernels too (thanks to a little trick which I backported from Intrepid).
The name of the package for Intrepid is nvidia-glx-173.
Release Highlights:
Added support for GeForce 8600 GS.
Fixed a problem with missing rendering in OpenGL Workstation Overlays.
Fixed a problem with running some SDL applications and virtual terminal switching.
Fixed a potential crash in nvidia-settings when saving to the X configuration file.
Improved error recovery paths in the case of corruption of the commands sent to the GPU.
Please test the driver (for Hardy) and report your experience with the driver in this bugreport.
NOTE: the driver has been uploaded today but should be available tomorrow.
17:33
As promised in my previous posts, in this blog post I will deal with a project I’m working on which implements this blueprint.
Bryce Harrington (the mentor of this blueprint), Colin Watson (the approver) and I talked about this at the UDS in Prague. The blueprint is based on Bryce’s original idea to improve the Screen Resolution panel. The work was divided into 2 phases:
Phase 1 (which is a higher priority) is about providing the Screen Resolution panel with the capability to set the virtual resolution in the xorg.conf when, put simply, 2 or more screens don’t fit the framebuffer. Currently the Screen Resolution panel doesn’t succeed in such case since the drivers are not able to reallocate the framebuffer yet. A simple GUI should allow users to set the required virtual resolution and write the settings to the xorg.conf through PolicyKit.
Phase 2 is about adding an “Advanced settings” button to the Screen Resolution panel so as to allow advanced users to edit the xorg.conf through a simple GUI. The aim of such program is not to set up multiple screens layouts but only to make it easier for users to add, edit and remove options without having to know which section an option, say, DontZap, belongs to, or to switch to a different driver. A more detailed explanation of the use cases is available here.
In Prague we agreed that this project couldn’t become reality without an xorg.conf parser/writer and some other tools. For this reason I started the X-Kit project:
Components:
* XorgParser: a simple, transparent and easy to extend xorg parser.
* XorgValidator: a program which uses X-parser, tries to make sense of xorg.conf and operates accordingly.
* Xorg Options Data Store: a program which translates the content of the manual of the xorg.conf into an XML file.
* Xorg Options Editor GTK: a simple GTK GUI to the xorg.conf.
* Xorg Options Editor KDE: a simple GTK GUI to the xorg.conf.
NOTE: all the code is in Python
Aim:
* a desktop agnostic kit to manipulate the xorg.conf (and whatever will replace the xorg.conf in the future).
Advantages of XorgParser:
* Simple API.
* Easy to extend.
Current Status:
* XorgParser: version 0.3 is available. You can get the code from my bazaar branch or from my PPA
* XorgValidator: there is already some code in place which I haven’t released yet.
* Xorg Options Data Store: the program is complete, works well and will be released soon.
* Xorg Options Editor GTK (aka Phase 2): the program is almost complete and will be released soon. You can have a look at this screencast to see how it works.
* Xorg Options Editor KDE: not started yet
* Phase1: the Python part is complete and, as you can see in this screencast, it works well. The screencast, however, doesn’t reflect the current status of phase 1 but still gives an idea of how this will work in practice.
For further details on the project, please have a look at the wiki.
A special thanks to Bryce Harrington and Martin Pitt whose feedback on the parser was extremely important.
18:59
What is ready
Currently there are 4 flavours of the NVIDIA driver: 177, 173, 96, 71.
They are all compatible with Xen and work only with 2.6.26 kernels (no 2.6.24, sorry).
They all use DKMS therefore you will have to keep the linux-headers installed.
CUDA is now supported by default (drivers 173, 177).
The packages can replace each other without any need to remove one driver before installing the other. All it takes is a simple “sudo apt-get install nvidia-glx-VERSION”.
NOTE: these drivers won’t be backported to Hardy. The “-envy” flavour in multiverse will be kept updated on Hardy.
Problems
xorg-server 1.5
The xserver was updated to version 1.5, which broke the ABI compatibility. As a result, drivers 96 and 71 (and fglrx) dont’ work with the new xserver and unfortunately the -IgnoreABI option of Xorg doesn’t solve the problem. This is something that only NVIDIA can solve. (177 and 173 work well)
Dist-upgrades
Currently when you dist-upgrade from Hardy to Intrepid, there is no way to update an old driver, say, nvidia-glx-new, to a driver with the new name scheme, say, nvidia-glx-173. You will have to install the driver manually with, for example, “sudo apt-get install nvidia-glx-173″ (there’s no need to uninstall the previous driver, since it will be replaced by the new one).
Currently we can’t rely on dependencies to make dist-upgrades smooth. If you compare the situation in Hardy with the one in Intrepid and especially if you think that NVIDIA could add and remove the support for more models to/from their drivers in the future, you will see why relying on dependencies wouldn’t be the best choice now.
SITUATION IN HARDY:
nvidia-glx-new (169.12):
Geforce 5xxx, 6xxx, 7xxx, and a few models of the 8xxx seriesnvidia-glx-new-envy (173.14.09):
Geforce 5xxx, 6xxx, 7xxx, and a few models of the 8xxx seriesnvidia-glx, nvidia-glx-envy (96.43.05) in Hardy is a legacy driver which supports:
Geforce 2xxx, 3xxx, 4xxx, 5xxx, 6xxx, 7xxx up to 7800nvidia-glx-legacy, nvidia-glx-legacy-envy (71.86.04) is another legacy driver which supports:
RIVA TNT/2, Vanta/Vanta LT, GeForce 256, GeForce DDR, GeForce2, Quadro2
Pro
SITUATION IN INTREPID:
nvidia-glx-177 (177.13):
Geforce 6xxx, 7xxx, 8xxx, 9xxx, GeForce GTX 260, GeForce GTX 280nvidia-glx-173 (173.14.09):
Geforce 5xxx, 6xxx, 7xxx, 8xxx, 9xxxnvidia-glx-96 (96.43.05):
Geforce 2xxx, 3xxx, 4xxx, 5xxxnvidia-glx-71 (71.86.04):
RIVA TNT/2, Vanta/Vanta LT, GeForce 256, GeForce DDR, GeForce2, Quadro2 Pro
As Martin Pitt suggested, we could have metapackages for each card series so that, for example, if NVIDIA decides to drop the support for GeForce 6xxx from driver 177, we can make the metapackage depend on driver 173 instead of 177. This is something which we might do in the next future when the hardware database for Jockey is ready. In the meantime we have no way to see which card series a card belongs to by relying only on its pci-id. Therefore we are working on an alternative solution (see the “Plans” paragraph).
nvidia-xconfig
Please be careful if you’re planning to use nvidia-xconfig. Xorg-server 1.4.99.901 removed support for the RgbPath option but nvidia-xconfig will add the following line to the “Files” section of your xorg.conf:
RgbPath "/usr/lib/X11/rgb"
You will have to comment it out.
NVIDIA should fix this soon.
Jockey
Jockey doesn’t support the new NVIDIA drivers yet, therefore you shouldn’t use it to install the NVIDIA driver (yet). I’ll work with Martin on this so that Jockey can keep rocking as usual.
Plans
Dist-upgrades
We will handle 2 cases: dist-upgrades done through Update Manager and the ones done from the command line.
Update Manager
If any version of the nvidia driver (with the old name schemes) is installed, basic hardware detection should be performed and the appropriate driver should be installed.
Command line
If the dist-upgrade is done from the command line we can’t install the appropriate driver automatically during the dist-upgrade (you can’t call apt while apt is in use). As Martin suggested, all we can do is warn our users through debconf so that they will know what to do. I have already implemented Martin’s idea by creating “nvidia-common”, which you can find in my PPA (NOTE: this is not the final release).
How does nvidia-common work?
nvidia-common depends on 4 new packages (nvidia-VERSION-modaliases) which contain the lists of the pci-ids of the NVIDIA cards supported by NVIDIA’s proprietary drivers. Such lists are generated automatically when the packages of the drivers are built therefore, when a driver is updated, its list of pci-ids will be updated too.
My Python program will detect the pci-id of your card and find the newest driver which supports it. If you have more than 1 one card plugged in, then it will look for a driver which supports all your cards and install that if available, otherwise the newest driver will be chosen (since I guess that you would prefer using your GeForce 9xxx rather than your GeForce 2).
This check is (currently) triggered in 3 cases:
1) when nvidia-common is installed
2) when the kernel image is installed/updated
3) when the kernel headers are installed/updated
If you haven’t a driver with the old name scheme installed or if your card is not supported you won’t see any debconf dialog, otherwise you should see something like this:
How to test it on Hardy:
add my PPA to your software sources:
deb http://ppa.launchpad.net/lrm-intrepid/ubuntu intrepid main
and install only nvidia-common (revision ubuntu12 or higher) and let it install its dependencies (i.e. the modalias packages). Then disable the PPA. Do NOT install any other package. You should see a debconf screen. The same will happen if you reinstall the kernel headers or image.
Backports
The drivers will be updated in the backports repositories as they will be actually backported from Intrepid+1 to Intrepid.
Credits
Ben Collins:
gave me some tips on TLS for the drivers.
Bryce Harrington:
has been very available and has followed all the steps of the migration to the new NVIDIA drivers.
Mario Limonciello:
tested the packages and gave me a few useful tips.
Martin Pitt:
guided me through the migration and has been very available. He gave me a lot of feedback on the packages, on the new name schemes and on how we should deal with dist-upgrades. His experience has been invaluable. Furthermore he is doing all the uploads for me.
Timo Aaaltonen:
did the merge of the Debian package with my initial package (hoping that the changes could be merged back into Debian) thus providing me with a new base to work on.
Furthermore he suggested the use of a dynamic dependency on the server ABI (so that we don’t have to hardcode it in the source) like the Intel driver does.
9:52
It took me some time to update the FGLRX and the NVIDIA driver in Ubuntu since I’m working on the drivers for Intrepid and on my new projects for Ubuntu. Furthermore driver 173.14.09 breaks the compatibility with realtime kernels and I didn’t want to upload something which would cause problems to a lot of users. For this reason I have written a patch (thanks to mizvekov from the NvNews forums for the tips) which will fix this problem while keeping the compatibility with non-realtime kernels.
Both the NVIDIA and the FGLRX contain a lot of fixes and I need your help to test the packages so that we can get them into hardy-updates (i.e. the stable repositories) soon. Please report your experience with the driver in this bugreport.
NOTE: the instructions to enable and use -proposed are in the bugreport (see Martin’s link)
22:00
Today, I’ve uploaded the latest release of the NVIDIA driver (173.14.05) to the the hardy-proposed repository (you should thank the Ubuntu-SRU and the MOTU-SRU teams for this). This is the bugreport containing the request for a SRU (Stable Release Update). Please test the new driver and post your comments there so that we know whether the driver works well for you too, and if it does, the update will be moved to the stable repository.
NOTE: this update won’t affect Ubuntu’s official linux-restricted-modules but only the linux-restricted-modules-envy so that nothing will break if you use the former.
Instructions:
All you have to do in order to test the new driver is enable the hardy-proposed repositories, refresh your list of packages and:
1) if you have already installed the driver through EnvyNG you should receive an update through Update manager
2) otherwise you will have to install and launch EnvyNG and select the “Manual selection of the driver” (since I haven’t had the time to update EnvyNG’s compatibility list for the automatic detection).
News:
I promised that I would blog about the projects I was assigned at the UDS and here’s the first news: I’ll maintain the NVIDIA driver for Ubuntu Intrepid together with Timo Aaltonen while Mario Limonciello will take care of the ATI (fglrx) driver. We’ll use DKMS for both drivers.
Stay tuned for more news and please help us testing the driver.
P.S. I’m working on the latest ATI driver too
17:08
I’ve been experiencing problems with people who said that they had sent me emails which I never received. I thought there were some temporary problems with my mailbox (with alice.it) since it’s not unusual to see the pop server complaining for nonsensical reasons.
This morning I noticed that I had no new messages in Evolution (my email client of choice) and this was a bit weird since I’m subscribed to a few mailing lists. I tried accessing my mailbox from alice’s web interface and, while it was true that there were no new emails, I noticed that there were about 860 emails in the junk folder, even though I had never set up a junk filter. A lot of emails were spam but a number of other messages were not. The website says that the emails in the junk folder are automatically deleted after 20 days. Now I’m wondering how many emails I lost all these years thanks to such a smart junk filter (which I hope I have disabled for good now).
If you sent me an email and didn’t receive a reply, it is very likely that alice’s spam filter is to blame.
P.S. If you sent me an email on adding the latest release of the graphics driver then I’ve definitely received a lot of them but I haven’t replied yet since I’ve been very busy with some new projects which I hope to be able to show soon. I will blog about the new drivers soon too since, in case you had doubts, I’m working on them.
16:50
I haven’t blogged for a while since I’ve been very busy and and I was too tired to blog or to do any actual work on my projects. This was my 1st time at the UDS and my 1st time abroad. It was a dream-like experience and went far beyond my expectations. I have met lots of interesting people ranging from developers to forum staff. We discussed about the new features in Ubuntu Intrepid 8.10 and, as a result, a few non-trivial tasks have been added to my todo list (I’ll blog about this later). The sessions were very well organised and the topics were extremely interesting but unfortunately I couldn’t attend them all at the same time.
We had a lot of fun and I would like to thank all the people who contributed to make this UDS rock.
In case you haven’t noticed, I appeared in some photos on flicker and in some blog posts:
Here are a few photos taken with Emanuele Gentili’s camera with some very interesting people.
myself, Mark Shuttleworth and Emanuele Gentili
Martin Pitt and I
Emanuele Gentili, Timo Aaltonen and myself
Emanuele, Henrik Nilsen Omma and myself
Agostino Russo, me and Emanuele
myself and Emmet Hikory
me, Scott Kitterman and Emanuele
Emanuele, Rob Savoye (the GNASH guy) and myself (a special thanks to MaryBeth Panagos - the girl in the background - who provided the nice “Gnash Cygnal” logo).
WARNING: talking to Rob about programming will dramatically decrease your self-esteem. He’s a genius.
A creepy guy on the 3rd floor… 
11:16
It’s been a month since my last blog post. EnvyNG was included in Hardy but it had a few problems and I have worked to fix them. I can’t upload such fixes since Hardy is a stable release. This means that all the updates will have to be tested before they are moved to the stable repositories. This is why I need your help. The more users test the fixes the sooner we can get them into stable.
Special Thanks:
All this wouldn’t have been possible without the amazing support of Martin Pitt, who guided me and helped me with the SRU (Stable Release Update). He has spent a lot of time on EnvyNG, gave me a lot of extremely useful suggestions, therefore I can say that you should really thank Martin for this release.
Timo Aaltonen brought bugs #212648, #186382, #118605 to my attention and suggested the solution. In case you don’t know it already, he’s one of the guys who take care of Ubuntu’s restricted modules. Keep up the good work, Timo!
A stripped down list of Changes:
envyng-core (1.1.1ubuntu15) hardy-proposed; urgency=low
* Fix (LP: #224004) Update NVIDIA compatibility list.
* Fix (LP: #221304) Use the new l-r-m-envy packages now.
* Install -envy packages instead of the ones in main
* Hide FutureWarning caused by python-apt
* xorgconfig2 now ignores sections which are not relevant in xorg.conf
linux-restricted-modules-envy-2.6.24 (2.6.24.500-500.28) hardy-proposed; urgency=low
* Fix (LP: #228649) xorg-driver-fglrx-dev conflicted with
xorg-driver-fglrx
* Sync with the fixes in linux-restricted-modules-2.6.24 (2.6.24.12-17.36)
* nvidia: Do not divert libwfb.so, because if the xserver provides one
it should be used. This caused at least problems with some websites
crashing on certain pages (see #212648), and pink shadows with compiz.
(see: #186382)
* fglrx: Patch authatieventsd.sh to search for xauth files in
/var/run/xauth/. Otherwise the session would freeze on logout for KDM
users. Thanks Ilja Pavkovic! (see: #118605)
* Remove previous diversions of libwfb.so in the postinst. Thanks Timo
Aaltonen.
* Make sure that any previous module of fglrx and nvidia built by DKMS are
removed before the new module is built and installed.
* Use -envy so as not to conflict with Ubuntu's lrm
* Add fglrx driver 8.4
Envyng-core will also fix the problem which prevented the QT interface from working properly.
EnvyNG now relies on its own packages (available in multiverse) therefore you will have to install the driver from EnvyNG again so that the correct packages are installed. If you don’t do it you will keep using Ubuntu’s default restricted modules. Of course DKMS, CUDA, etc. are back in my packages.
The latest release of ATI’s proprietary driver (8.4) is also available and contains a patch which should fix bug #118605 (which doesn’t solve the problem on my computer though).
How to test it:
You will have to enable the hardy-proposed repositories (Go to System/Administration/Software Sources/Updates and select “Proposed Updates (hardy-proposed)”) and upgrade to envyng-core (1.1.1ubuntu15), then launch EnvyNG and install the drivers.
Where to report:
If you have problems with EnvyNG (e.g. if EnvyNG crashes during the installation of the driver) you can report them here.
If you have problems with the drivers which EnvyNG installed you can report them here.
You can simply add a comment to one of the bugreports which you will find at these links if your problems are related to those reports or if you just want to confirm that either EnvyNG or the drivers work well for you (this will really help us).
If you want you can use this model to report:
Used EnvyNG (yes/no):
Worked with Ubuntu’s default restricted modules (yes/no):
Graphic card model:
Problem (solved/otherwise describe the problem):
Example:
If it works for you:
Used EnvyNG: yes
Worked with Ubuntu’s default restricted modules (yes/no): yes
Graphic card model: Geforce 7300GT
Problem: solved
OR if it doesn’t solve the problem
Used EnvyNG: yes
Worked with Ubuntu’s default restricted modules (yes/no): yes
Graphic card model: Geforce 7300GT
Problem: NVIDIA driver 169.12 still freezes my computer when I visit this website…
NOTE:
I’m working on this Bug too.
16:15
I’m working on EnvyNG every day. I’m fixing as many bugs as possible. Here’s a list of what’s changed in EnvyNG and Envy Legacy:
Improvements in EnvyNG-core:
* New connection detection method (based on Network Manager)
* Update compatibility list
* Update translations
* Use unicode (utf-8) for the translators' names
* Use an additional xorg.conf parser in order to set the default colour depth
EnvyNG checks the availability of an Internet Connection either by asking Network Manager (through dbus) or (if you don’t use network manager) by using only Python’s “urllib2″. This solves Bug 211620.
The latest update of EnvyNG-core includes an additional xorg.conf parser which should finally solve the problem with ATI cards which don’t have a “defaultdepth” option set in xorg.conf. This made the Xserver crash (at times?) since the fglrx driver assumed that the default colour depth was 8bit.
Improvements in EnvyNG-qt:
* The links in the about dialog can be selected with the mouse cursor
* Fix complete dialog showed up when restart dialog should have
* About dialog can expand now
* Fix if both EnvyNG-qt and -gtk are installed, -qt should be the one which is launched on KDE
Improvements in EnvyNG-gtk:
* GTK filechooser points to /home by default
Bugfixes in Envy Legacy:
* Fix Bug #210392 in classes
* Catch exception in classes.restorenvfolder()
* Add "n/a" to dkms blacklist so the unofficially dkms is not installed
on Debian Lenny (Lenny is still unsupported)
Should you find other bugs, please report them to me.
18:38
I’ve set up a new PPA repository for Hardy containing EnvyNG 1.1.0. The repository includes a new version of the three packages with a few bugfixes.
Add this line to your /etc/apt/sources.list so as to be sure to get always the latest release of EnvyNG :
deb http://ppa.launchpad.net/envyng-hardy/ubuntu hardy main
Update your list of packages:
sudo apt-get update
and then, for the textual installer, type:
sudo apt-get install envyng-core
or for the GTK GUI:
sudo apt-get install envyng-gtk
or for the QT4 GUI::
sudo apt-get install envyng-qt
I have followed your suggestions and I’ve fixed a few inconsistencies in the QT4 interface, therefore I need you help again with the translations for just 1 word (”Cancel”). I’ve tried to use what Rosetta suggested as alternative translations from other packages (i.e. firefox 3) therefore some translations will look like they are complete but please check that everything’s ok even in such case.
Thanks again.
P.S. please keep reporting bugs so that I can fix them ASAP.
EDIT: I had posted the wrong repository. Sorry for the inconvenience.
18:01
Here is a new release of EnvyNG (which supports only Ubuntu Hardy). EnvyNG 1.1.0 is made up of 3 packages:
Brief Explanation
If you install only envyng-core you will have only the textual interface which (currently) has less features than the 2 GUIs.
If you want to install either envyng-gtk or envyng-qt you will have to install envyng-core first.
New Features
The 2 GUIs now enable you to:
1) Install and save the packages with the driver to a folder
2) simply download the packages without installing anything (this will be useful if you want to install such packages on a computer which is not connected to the Internet)
EnvyNG relies upon my PPA repository (the packages are no longer built locally), therefore every time a new driver is released I will only have to update my repository and you won’t have to install a new release of EnvyNG. You will receive the update via update manager. The packages use DKMS (i.e. you won’t have to reinstall the driver for each kernel you have since this is done automatically), do not conflict with Ubuntu’s linux-restricted-modules, do not cause problems during dist-upgrades since they can be overwritten by Ubuntu’s official packages (if they provide a driver which is newer than the ones in my repository or if the kernel is upgraded, say, from 2.6.24 to 2.6.25, ABI bumps won’t do anything).
Translations
There was a problem with Launchpad therefore I wasn’t able to upload all your translations in time (but I promise I will ASAP). Thanks again for your translations.
Instructions
Please read point A of the FAQ before you install EnvyNG (so that the old EnvyNG doesn’t conflict with version 1.1.0)
Testers
Please test the packages and let me know if there are problems.
Credits
As I said in the past, I would have never done all this alone. I would like to thank all the Ubuntu developers who helped me, all the artists who participated in the artwork contest, and the translators. And special thanks to Carlos Perelló Marín who helped me with Rosetta.
14:37
I’m still trying to get over the stress of graduating, dreaming (every night!) of having yet to do exams in order to graduate doesn’t help though. I’m working on my projects at a slower pace, fixing a few bugs here and there before the release of EnvyNG. I have designed a new system for URandR and I hope to write some real code soon.
Today I have fixed a nasty bug in the old EnvyNG which affected automatic hardware detection with the following ATI cards:
['ATI FireGL V7300', 'ATI FireGL V7350', 'ATI FireGL V7350 Secondary', 'ATI FireGL V3400 Secondary', 'ATI FireGL V7300 Secondary', 'ATI FireGL V5200', 'ATI FireGL V3300 Secondary', 'ATI FireGL Z1 Secondary', 'ATI FireGL X3-256 Secondary', 'ATI FireGL X1 Secondary', 'ATI FireMV 2200 Secondary', 'ATI FireGL V3200', 'ATI FireGL X3-256', 'ATI FireGL Z1', 'ATI FireGL V5200 Secondary', 'ATI Mobility FireGL V5200', 'ATI FireGL X1', 'ATI FireMV 2200', 'ATI FireGL V3100', 'ATI FireGL V3300', 'ATI FireMV 2200 PCI', 'ATI FireMV 2200 PCI Secondary', 'ATI FireGL 8800', 'ATI Mobility FireGL V5000', 'ATI Mobility FireGL V5000', 'ATI Mobility FireGL V5250', 'ATI Mobility FireGL V7200', 'ATI FireGL V5100', 'ATI Mobility FireGL V3100', 'ATI Mobility FireGL V7100', 'ATI Mobility FireGL V3200', 'ATI FireGL V7200 Secondary', 'ATI FireGL T2 Secondary', 'ATI FireGL V7200 Secondary', 'ATI FireGL T2', 'ATI Mobility FireGL T2/T2e', 'ATI Mobility FireGL V5100', 'ATI FireGL V5100 Secondary', 'ATI FireGL V7100 Secondary', 'ATI FireGL V3100 Secondary', 'ATI FireGL X2-256/X2-256t Secondary', 'ATI FireGL V5000', 'ATI FireGL V3300', 'ATI FireGL V5000 Secondary', 'ATI FireGL V7200', 'ATI FireGL V3200 Secondary', 'ATI FireGL X2-256/X2-256t', 'ATI FireGL V7200', 'ATI FireGL V3400', 'ATI FireGL V7100']
It’s all fixed in EnvyNG’s new release.
As regards the translations for EnvyNG 1.1.0, you’re doing an amazing job. Thank you all. One thing that I’ve noticed though is that a few translators are having problems with the translation of the word “Main”, maybe because it’s a rather generic word which doesn’t make much sense out a context. Here is screenshot which hopefully will make things a bit clearer (”Main” is the label of the 1st tab):
16:48
Dear users of EnvyNG,
if you want to help to translate EnvyNG (1.1.0) into your native language you can contribute by using Rosetta’s web interface.
The Italian translation is complete.
As regards the EnvyNG 1.1.0, it will no longer build the packages locally but will rely on my repository so that you won’t have to install all those dependencies anymore. This means that when a new driver is released you will only have to wait for me to update my repository (rather than having to install a new release of EnvyNG).
EnvyNG 1.1.0 is ready (but I haven’t released it yet), therefore the sooner the translations are available, the better.
Thanks in advance for your help.
P.S. the %s symbol must be left as it is.
15:42
If you were affected by this bug in the ATI installer on Ubuntu 64bit, the new release of Envy Legacy (envy_0.9.10-0ubuntu8) fixes it.
EDIT: please try envy_0.9.10-0ubuntu9 instead
10:12
First of all I would like to thank all the ones who contributed to EnvyNG with their icons and logos. You all did an amazing work. I received many works and they were simply beautiful, therefore it was very hard for me to choose only one. My choice is based on my (questionable) personal taste and on my (anything but clear) idea of what EnvyNG should look like, therefore I don’t expect everyone to agree with my decision.
In the end I chose Alberto Gasparin’s icon and logo which I find beautiful, stylish and representative of the spirit of EnvyNG:
Here is the list of the artists (for once in inverted alphabetical order) who created the other wonderful icons and logos:
Valerio Tarabella
Tommaso Gardumi
Simone Zuliani
Simone Scalas
Sergio Gridelli
Seaofgrass
robilive
rigobot
Michael Gatta
Julian Saraceni
Jonathan Grass
Jesús Alonso Abad
Jack Eatnins
Ivan Prignano
Hussanin Al Hammady
George Connor
Frank Quotschalla
Federico Pelloni
excalibur1491
Eduardo Ruiz
deviantdark
Davide Candita
Daniele Reviglione
Damiano Dallatana
Antonio Acquarica
Anton Petersson
Thank you very much, you all rock!
P.S. You will read more about EnvyNG soon
8:36
If you are affected by bug 204044 with the ATI driver, please try envyng_1.0.4ubuntu11.
Let me know if there are still problems.
EDIT: The problem with fglrx and DKMS is solved in envyng_1.0.4ubuntu12
15:56
This morning I defended my thesis (in foreign languages) whose title was “Language and Artificial Intelligence”. I experimented a bit also with chatterbots and I had corrected and modified Joe Strout’s therapist (written in Python), added a few more patterns and added the support for Espeak (a voice synthesiser). I had to present my work and then chat to the chatterbot (which I called “Alberta”) so as to show how it could trick us into thinking that we are dealing with a human being (in limited contexts).
I made my laptop (running Hardy with Compiz) resume from standby, I used URandR to clone the content of my screen on the beamer and then the audio decided to crash. What the heck???
I tested the program 2 days ago with the same projector and audio cable and it worked well. *Of course*, after my graduation both my program and Ubuntu worked well… I should have restarted my computer but I was running out of time.
I also told the commission that something similar happened to Bill Gates
I explained what my program was supposed to do, etc. and, as you can see in this photo, the defence of my thesis went great. I really can’t complain.
Here I was explaining what happened to my laptop to a friend of mine:
Of course now that I graduated I am also unemployed, therefore I’m officially looking for an IT job (better if located in Europe).
16:05
A few days ago I decided to have a deeper look at the API of the Python bindings for Xrandr (pyxrandr) written by Sebastian Heinlein and Michael Vogt. While I must admit that they did a good work with the bindings I’m still not completely satisfied with what I can do with them. This is not a complaint, actually I’m quite happy since it will give me a reason to learn C and complete the bindings myself (when I have the time). In the meantime I will use such bindings in URandR in at least 2 ways:
1) To achieve compatibility with drivers which support only RandR 1.1 (such as “nvidia”, “fglrx”, etc.)
2) To drop hardcoded names of the outputs for the sake of a more dynamic detection
As regards point 1, this screenshot shows how URandR works with NVIDIA’s proprietary driver as well:
If a driver doesn’t support RandR 1.2 you will only be able to change its resolution, refresh rate and to rotate the screen. This means that I won’t have to check which driver you’re using by reading your “/proc/$(pidof X)/maps”, which requires having root permissions. If URandR can get the current rotation of the screen through the xrandr bindings then the driver supports RandR 1.2, otherwise URandR will use compatibility mode.
Thanks to point 2 I won’t have to worry about the names by which each driver refers to output connections. For example this table contains the names of the outputs used by the ATI (radeon) driver and by the Intel driver:
| Ati (radeon) |
Intel |
| VGA-0 | VGA |
| LVDS | LVDS |
| DVI-0 | TMDS-1 |
| S-video | TV |
I assume that drivers such as radeonhd, nouveau, etc. which support RandR 1.2 use other names. Fortunately I’ll no longer have to deal with their idiosyncrasies (directly) since the xrandr python bindings give URandR access to such names at runtime. Another thing I won’t have to worry about is the number of monitors, tvs, etc. that you connect to your graphic card. If you can connect 20 screens at the same time (provided that such thing is possible and that the driver supports it) URandR will detect them all. Thanks to these changes I was able to improve my own detection library (which is *a bit* more readable) and to make it much more dynamic as well.
Here are my plans for the next release of URandR:
* Support for RandR 1.x (DONE)
* Support for any driver which supports RandR 1.2 (DONE)
* PolicyKit integration - so that you don’t have to
be root in order to run URandR and that if the
framebuffer is not enough URandR can ask your
root password only to set the virtual resolution
in your xorg.conf
* When you apply your settings, things can go wrong,
therefore URandR will show a dialog with a countdown
and a button which, if not clicked in time (if for example
you disabled your main screen by mistake), will revert to
your previous settings.
When the new URandR is ready I will work on an alternative interface in QT4.
Here are a two screenshots of URandR with the Intel driver with my laptop screen (LVDS) (virtually) positioned to the left of an external monitor (VGA):
As you can see, each output has its own place in the treeview instead of having its own tab.
When will all this be available? I don’t know, however I’m going to graduate (yes, again…) next week therefore I guess I’ll have (relatively, as usual…) plenty of time to work on URandR.
11:18
The ATI Catalyst driver 8.3 is now available in Envy Legacy and EnvyNG. You can check the release notes of the driver here.
As regards the future of EnvyNG, I’m glad to say that the GTK GUI for EnvyNG 1.1.0 is finished and the QT4 interface is in good shape. I only have to solve a problem with the logger in QT4 since using QProcess and TextEdit as a virtual terminal (a la VTE) makes the log look a bit weird. I’ll write a post about this.
EDIT: if you had problems with Envy Legacy and the ATI driver, try version 0.9.10-0ubuntu7
11:51
EnvyNG (1.0.4ubuntu2) is now available.
Here is a stripped down changelog:
* Defaultdepth is set to 24bit in xorg.conf as required because of BUG #94963
* Added: NVIDIA driver 169.12
* Changed: ATI packaging scripts are now based on Ubuntu's lrm
* Added: ATI driver 8-02
* Added: NVIDIA driver 96.43.05 and 71.86.04
* Added: patch for xen kernel 2.6.24 and NVIDIA driver 169.0x
Thanks to Kano for reporting the problem and the solution.
* Added: patch for rt kernel 2.6.24 and ATI driver
Thanks to Kano for reporting the problem and the solution.
* Changed: DKMS patches the NVIDIA driver if necessary.
* Changed: nvidia-settings is installed from the repos for all the driver
flavours.
* Changed: NVIDIA's libglx.so.$VERSION is now installed to
/usr/lib/xorg/modules/extensions/ rather than in
/usr/lib/xorg/modules/
* Added: NVIDIA support for DKMS
* Changed: the NVIDIA driver now depends on DKMS
* Changed: there no longer is a popup which asks users whether they want to
let EnvyNG configure their xorg.conf. It's all done
automatically.
* Changed: when a driver is uninstalled, the driver in xorg.conf is set to
an open source driver (as in the --uninstall-all mode)
Features
Have a look at this blog post
I have updated the FAQ for EnvyNG which I suggest you to read. For example you will learn that you will have to launch Envyng with “envyng -t” rather than “envy -t” from the command line or that you will have to remove the old Envy before you install EnvyNG (see point A).
Special thanks:
Without their help there would have been no EnvyNG. I think it was Daniel who suggested the creation of a page on the wiki titled “EnvyNG”. I liked the name and this is how EnvyNG was born.
I must admit that working with (Ubuntu and non-Ubuntu) developers who are *a bit* more experienced than me is *slightly* better than working on my own. It was a real pleasure. I look forward to working with them again in order to improve the linux-restricted-modules and (hopefully) many other things in Ubuntu.
This community rocks 
P.S. Enjoy this new release and let me know if you have problems with it
EDIT1: I have just fixed a bug which affected the ATI driver. The fix is in EnvyNG (1.0.4ubuntu4)
EDIT2: I have just fixed a bug which affected the NVIDIA driver (all versions but the latest). The fix is in EnvyNG (1.0.4ubuntu7)
15:17
If you use an operating system other than Ubuntu Hardy you will now have to use Envy Legacy. Envy New is dead and will be soon replaced by EnvyNG.
Release highlights of Envy Legacy:
* Fixed: Envy tried to install dkms on Debian.
* Fixed: the GUI didn't show the missing dependencies which can't be installed.
* Added: Nvidia drivers 96.43.05, 71.86.04
* Added: AMD Catalyst driver 8.02
Enjoy
EDIT: there was a problem with the ATI driver which I have just solved. Please download Envy Legacy again
EDIT 2: I have updated the NVIDIA driver to version 169.12
13:25
First of all I would like to thank you all for participating in the contest. I apologise if I didn’t reply to all your emails but I’m receiving so many emails that it’s hard to keep pace with your emails. I’m so busy doing the uploads of your work, coding EnvyNG and living my life (but only in my spare time)… anyway I just wanted to let you know that you ROCK and that I do appreciate all the effort you’re putting into your works.
I have set up a new gallery with all your logos (with thumbnails) so that I don’t have to edit html code every time I receive a new logo. I will only have to upload the new logos and the php scripts which I’m using (LGR Photo) will update the gallery for me.
NOTE: unfortunately the script supports only .jpg.For this reason I had to convert all your works to jpgs therefore the quality of the images in the gallery may be poorer than the one of the originals (which I will use for EnvyNG). If you know a php script with supports pngs and svgs, and which creates albums from folder structure, please let me know.
I would like to make it clear that there’s no rush to create and send me your works since EnvyNG 1.1.x is still under heavy development. EnvyNG 1.0.x won’t include the new GUI and hasn’t been released yet.
Here’s something I managed to do yesterday (despite the fact that I hadn’t slept at all the night before):
The error dialog (of the QT4 interface) shows what prevented the installation process to end successfully in EnvyNG. You will be able to copy and paste the content of the text browser in dialog (hopefully) without having to send me the full log.
QT4 is great
Of course I’ll do something similar in GTK as well.
13:08
The reactions to the screenshots of the prototypes of EnvyNG 1.1.x were positive however some users (see the comments to my previous posts and this blog post ) led me into thinking that it’s time for me to change EnvyNG’s icon and logo.
I won’t draw a new icon and logo myself though. I wouldn’t define myself as skilled with the GIMP or Inkscape therefore I need your help:
Requirements for the icons and logos:
For further details you can have a look at the Frequently Asked Questions.
Two Italian users have already sent me their logos. Of course your (polite) feedback on this blog is more than welcome.
Follow this link to participate.
EDIT: the new galley is here
15:42
Features in EnvyNG 1.1.x
The new GTK interface:
The new QT4 interface:
P.S. In case you’re wondering, I will update the good old Envy soon.
15:41
I have finished writing my thesis (in Latex) and I’ll graduate in March. In the meantime I’m studying PyQT4 and working on Envy.
I haven’t updated Envy yet as I’ve been working on EnvyNG (”NG” stands for “Next Generation”) i.e. the latest evolution of Envy. EnvyNG will support only Ubuntu Hardy (8.04) or higher while Envy Legacy will still support Ubuntu’s previous releases and Debian (stable).
The release of EnvyNG which you will see in time for Hardy is 1.0.x. Consider it a transitional release since many new features will be available only in version 1.1.x. Here is a (partial) list of the features in EnvyNG 1.0.x
I’ll reveal other details on version 1.0.x soon
In the meantime you might want to have a look at the list of features in version 1.1.x.
19:03
envy 0.9.10-0ubuntu2 adds the support for the latest Nvidia driver and fixes a bug:
* Fixed: Envy stopped after the process in the virtual terminal ended.
* Added: Nvidia driver 169.09
* Removed: Nvidia driver 169.07
Here are the release highlights from Nvidia’s website:
* Fixed a problem causing the fan on some GPUs to always run at full speed.
* Fixed a bug that caused the X driver to crash if the X.Org GLX extension module was loaded intead of NVIDIA’s.
* Improved the X driver’s awareness of the current notebook docking status.
* Fixed brightness control on HP Compaq notebooks.
* Fixed a bug in the Linux/i2c algorithm driver implementation that prevented core transfer types from succeeding.
Enjoy
19:54
AMD released new driver (8.01) which still lacks the symlink to libfglrx_gamma.so.1.0. Envy gets around the problem now. Let me know if you have further problems.
Here’s the changelog:
* Fixed: Upstream Bug - missing symlink to libfglrx_gamma.so.1.0 (libfglrx_gamma.so.1)
* Fixed: "Envy" was not the title of the legacy dialogues on Debian
* Added: AMD Catalyst driver 8.01
* Removed: AMD Catalyst driver 7.12
Make sure you check both the solved and the known issues before you install the new driver.
11:37
As you might already know, the latest release of the Nvidia driver includes the CUDA driver. Unfortunately the packages generated by Envy lacked the new files which made it possible to use the CUDA Toolkit (on both Debian and Ubuntu). This is no longer the case in envy_0.9.9-0ubuntu6 which I released about two days ago (but I was too busy and tired to announce it). Furthermore the wfb module of the NVIDIA driver wasn’t included in the packages generated by Envy because of a stupid typo.
Here’s the changelog:
* Changed: nvidia-glx-dev was not installed on Debian
* Fixed: Bug #180144 missing CUDA support on Ubuntu
* Fixed: Bug #180144 missing CUDA support on Debian
* Fixed: Bug #178291 Nvidia wfb module missing on Debian
NOTE: unless you need CUDA or you use Debian and the latest NVIDIA driver you will have no reason to install this new release.
On another note, this week I’ve been working on a website and I had to learn a bit of HTML DOM, Javascript, PHP, which I had *never* used. It was quite (painful but) interesting. Just to mention a problem I had, I was struggling with Internet Explorer when I discovered that it had a problem with Javascript’s array method indexOf(), which I had to create with “protoype” just for IE since it works well in Firefox. And of course making a website look good (and yes I do use CSS) in IE, Firefox and Opera at the same time can be a pain. If Firefox’s Firebug extension didn’t exist I think I would have never completed that website.
17:33
Here is the changelog of Envy’s new release:
* Changed: backported xparse and xorgconfig from Envy's unstable branch so as to
switch to the guidance backend
* Changed: backported improvements to Shutilities from Envy's unstable branch
* Changed: the latest release of the ATI driver is automatically installer for
ATI FireGL cards
* Added: objects.restorexorg()
* Fixed: Bug #179746 xorg.conf couldn't be modified because of a bug in xparse
* Fixed: nvidia-settings is no longer installed for the legacy driver because of
Ubuntu's Bug #156730
As you can see, this new release should solve a few problems and includes some backported parts of Envy’s next major release (0.9.10). Unfortunately the package “nvidia-settings” can no longer be installed because of Ubuntu’s Bug #156730. This problem affects only nvidia-glx-legacy (driver 7xxx) while the other two flavours of the driver are not affected since they already include “nvidia-settings” and therefore don’t need “nvidia-settings” to be installed. If you use the legacy driver, please use Ubuntu’s “Screens and Graphics” application (in the “System/Administration” menu) if you need to set up your screen resolution (or multiple screens).
As some of you might have noticed I have recently changed Envy’s web page since some users complained about its length and about its confusing structure. I’m not a web designer therefore don’t expect to see a masterpiece. If you have further suggestions regarding its usability, please let me know. I have also updated the FAQ for both Ubuntu and Debian.
NOTE: if Opera is your browser you will have to select the “Fixed Table Layout” option in the “View/Style” menu, otherwise the table on my web page will be as large as the entire page. I don’t know why this is happening since I can’t reproduce the problem using Firefox, Epiphany, Konqueror, Internet Explorer 6 (yes, even IE 6!!!)
17:55
A new release of Envy is available. Here’s the changelog:
* Added: Nvidia driver 169.07
* Removed: Nvidia driver 100.14.23
* Added: AMD Catalyst driver 7.12
* Removed: AMD Catalyst driver 7.11
ATI’s Catalyst driver 7.12 uses DKMS (thanks to Mario Limonciello), and I’m planning to add DKMS to the NVIDIA driver in Envy’s next release (0.9.10) (as well as other cool features). Thanks to DKMS you won’t have to reinstall the driver every time the kernel is updated.
Make sure you read the Release Notes and (especially) the Known issues of both the ATI and the NVIDIA driver before you install any of these drivers.
You can get the driver here.
Merry Christmas and a Happy New Year or, if you’re not a Christian, I simply wish you a good time
EDIT: if you need Envy’s previous release you can get it here:
Envy New
Envy Legacy
14:26
Today (thanks to Cyril Brulebois) I have found bug which in turn was cause by an ever nastier bug in URandR. The current refresh of a device was detected even if such device was not enabled (???) (i.e. plugged in but disabled). URandR knows that, if a device has a current refresh rate, such device must necessarily be enabled (otherwise the said refresh rate wouldn’t be called “current”).
The cause of this problem was so stupid that I’m sure it was the result of one of my late night coding sessions :-/
Please let me know if you have problems with this new release.
15:51
This new release of URandR will finally allow you to save your settings without touching your xorg.conf (except for the virtual resolution).
URandR can now check if you’re using independent screens or cloned screens as you can see in the following screenshot:
Furthermore you can now save your current settings to a profile. Currently there are four profiles which you can use to store your settings (home, office, conference, other). You might wonder what you can do with such profiles?
1) you can save your settings to a profile (e.g. your DVI screen is set to a resolution of 1600×1200 and is to the left of your laptop screen) and load them whenever you want without having to set the resolution and screen position every time.
2) you can choose to set a profile by default. so that when you enter your desktop your screens will be configured exactly as you want, without having to use URandR every time.
URandR doesn’t write your settings to the xorg.conf but uses profiles. Profiles are scripts containing all your settings. If you set a profile as the default profile, such script will be executed every time you enter a desktop session.
NOTES:
1) Only GNOME, KDE, XFCE are supported (therefore setting a default profile might not work with other desktop environments).
2) Only two screens are supported.
3) Your graphic driver must support RandR 1.2
4) The new packaging scripts will make URandR easy to install on Debian (thanks to Cyril Brulebois).
5) You will find URandR in the System/Preferences menu in GNOME and in the Settings menu in KDE.
You can get URandR here.
Constructive criticism is welcome.
P.S. Yes, I will give you a version of Envy with Nvidia’s beta driver before Christmas.
EDIT: Thanks to Alex Launi now URandR works well with ldap
18:38
Here is the changelog:
* Fixed: the detection of installed packages failed in certain cases
* Fixed: a few mistakes in the Norwegian and Russian translations
If Envy complained about the lack of some packages which it said it couldn’t install but which were already installed then this release will solve your problem.
Special thanks to cwillu, who made notice that I should have used dpkg --get-selections instead of dpkg --list. I’ll read the fine manual to the end in the future.
12:40
Envy Release Notes
• Desktop Effects with NVIDIA cards
∘ Try to enable the Desktop effects, let Restricted Drivers Manager install the driver again, then (don’t reboot) use Envy again and finally reboot.
• The ATI module couldn’t be loaded at times.
∘ usually a depmod -ae solved the problem but I’ve tried to fix the problem.
∘ I even managed to get the driver to work on Gutsy’s livecd (I had to log out and log in after the installation of the driver instead of rebooting, which I couldn’t do, but I warmly recommend you to reboot). The desktop effects worked also on the livecd (they were a bit slow though).
• The new ATI driver is available in Envy
• NVIDIA’s new BETA driver is not included in this release.
∘ I might release an unstable version of Envy for this. Later…
• Envy no longer depends on “nvidia-xconfig” to set up your xorg.conf
∘ Envy has its own Xorg parser now.
• The list of ATI/AMD cards has been updated
∘ Radeon HD cards should be automatically detected.
• You can either use Envy or Restricted Drivers Manager. Please don’t use them together.
∘ Should you decide to use Restricted Drivers Manager after using Envy you will have to undo what Envy did, by typing:
∘ sudo envy –uninstall-all
P.S. I’ll set up the repositories as soon as I have the time. In the meantime you can get Envy here.
12:57
Here is the changelog of envy 0.9.8-0ubuntu13:
envy (0.9.8-0ubuntu13) gutsy; urgency=low
* Fixed: Serbian localisation was used in a Czech locale environment
* Fixed: Corrections to the Russian translation
* Added: Czech translation
* Fixed: the description in debian/control didn't mention the ATI driver
as you can see, the Czech had to use Envy localised in Serbian and, since I doubt that all Czechs can speak Serbian, I think this is a useful update .
Translators:
Czech: Tomáš Klouda
I have developed a Xorg parser so as not to depend on “nvidia-xconfig” any longer. I’m quite happy with the result but I haven’t had the time to integrate this new module in to Envy yet.
This new module will allow me to simply tell it, for example, to add/change/remove an option to the “Device”, “Screen”, or “Extensions” section (in xorg.conf) with a command such as the following:
customoption('UseDisplayDevice', 'DFP', 'screens')
or the following:
customoption('Composite', 'Disable', 'extensions')
Stay tuned for more updates.
22:25
This new release will make your experience with ATI and the Desktop Effects a bit easier (in Ubuntu and in its derivatives). The fglrx driver was not included in Compiz’s whitelist in Ubuntu Gutsy, therefore ATI users were not able to use the Desktop Effects. Envy is now able to solve this problem for you (but it will restore the old whitelist if you uninstall the driver from Envy, in case you’re wondering). Of course the Desktop Effects will work only if you use the ATI driver 8.42.3.
I have cut (and resized) the logo since it didn’t fit certain screens in low resolution (please remember that the textual install should fit any screen). Furthermore the following translations were added: Danish, Norwegian, Romanian, Taiwanese, Ukrainian.
Translators
Danish: Søren Bjerrum
Norwegian: Kjetil Rydland
Romanian: nokia
Taiwanese: Jose Sun
Ukrainian: Artem Gluvchynskyj
P.S. You can get Envy here as usual
15:06
There are a few changes in this new release:
1) the new NVIDIA driver 100.14.23 is now available
2) the new ATI driver 8.42.3 is available, however I have to say a few things about it:
* Compiz might be a bit slow, at least on my X1600 (make sure you’re using Compiz 0.6 or higher)
* Driver 8.42.3 doesn’t support ATI Workstation cards (FireGL) therefore, if you own a FireGL card, Envy will install version 8.40.4
* As AMD admits in the release notes, version 8.42.3 doesn’t work with Debian/Ubuntu 64bit, however Envy uses a patch which fixes this problem (Thanks to Aric Cyr and Mario Limonciello)
3) Envy is now localised in the following languages: Russian, French, Finnish, German, Spanish (Spain), Spanish (Chile), Italian, Turkish, Dutch, Brazilian Portuguese, Portuguese, Austrian, Polish, Amharic (Ethiopian), Serbian, Slovak.
NOTE: only the GUI is localised. The textual installer is still in English.
4) I have modified “Envy legacy” so as to make work exactly like “Envy new” sure that I can maintain it without too much effort. As a result, localisation is available also in “Envy legacy”.
Translators
Amharic (Ethiopian): hb
Austrian: Paul Hoell
Brazilian Portuguese: Jose Nilton, José Tadeu Barros
Dutch: Alexander van Hoorn
Finnish: Jukka Kauppinen
French: Mathieu Velten, Christian Kaenzig, Omega13
German: Carlos Diener
Polish: Grzegorz Więcek
Portuguese: Walker Pt
Russian: Anton Starikov, Ivan Potapov, Nicholas Vavilov
Serbian: Zoran Olujic
Slovak: Michal BelloviÄ
Spanish (Chile): Cristóbal Tapia
Spanish (Spain): David Rando
Turkish: Serkan Çalış
NOTE1: if I forgot (or mispelled) your name, please let me know
NOTE2: if you want to translate Envy into your language, I’ll be glad to include your translation in the next release.
What makes open source projects rock?
It’s the amount of people passionate about it, willing to sacrifice their own spare time (or money) to contribute to open source projects.I would like to thank all the people who have helped this project with bug reports, donations, patches and translations. In other words You rock!
P.S. You can get Envy here as usual
13:24
I have added multilingual support to Envy’s next release, which is still under development, but so far I have added only the support for the Italian language as regards, the GUI. The textual installer will remain in English (at least in next release).
What can you do to help?
1) First of all install gettext:
sudo apt-get install gettext
2) download this file in you home folder.
3) Now there are two ways you can follow this step.
If your Operating System is localised in the language into which you’re planning to translate Envy (e.g. you want to translate Envy into Spanish and your OS is in Spanish) you can simply type this command:
msginit --input=envy.pot
Otherwise, if (like me) you’re using your OS in another language (I’m Italian but my Ubuntu is in English) you will have to type:
msginit --input=envy.pot --locale=the_desired_locale
Of course you will have to replace “the_desired_locale” with the language into which you want to translate Envy. For example if you want to translate it into Spanish you will have to put “ES” (so that it looks like this: “msginit –input=envy.pot –locale=ES”)
then you will be asked to enter your email address (and no, I won’t spam you ) and you will have your .po file (e.g. “es.po”)
4) you will have to translate a few lines just as I did in this example. The “msgid” contains the original text string while the “msgstr” is where you will have to put the translated string.
5) Remember to put your name in the msgstr related to the “translator-credits” msgid in your po file.
#: ../envyui/gtkenvy.glade.h:25
msgid "translator-credits"
msgstr "Alberto Milone"
6) Upload your .po file here:
NOTE: if you can’t upload the .po file you can email me the file:
[ you can find my email address on my website: http://www.albertomilone.com/ ]
And here is the result:
EDIT: so far I have received translations into:
Russian, French, Finnish, German, Spanish (Spain), Spanish (Chile), Italian, Turkish, Dutch, Brazilian Portuguese, Portuguese, Austrian, Polish, Amharic (Ethiopian), Serbian, Slovak
NOTE: you can see which translations are already available here
10:53
If you installed Envy New and you typed “envy -t” you might have noticed this error (which you can’t reproduce if you use the graphical installer):
Traceback (most recent call last):
File "interface.py", line 13, in
from instun import main
ImportError: No module named instun
This problem is fixed in envy_0.9.8-0ubuntu5.
Thanks for your feedback.
P.S. I’m planning to set up 2 repositories (1 for Envy New and 1 for Envy Legacy) so that you don’t have to update Envy manually.