Well, i'm not yet using Jaunty (still on Interpid) - and i got an annoying situation having both LXDE and Gnome installed - a dependence named lxnm, not only it's not working, as well it removes by conflict nm-applet (network-manager-gnome package), and if we insist reinstalling LXDE, we take the risk on being completelly offline (if we only have wireless access), like happened to me.
I think it were a MOTU 'disaster' on marking lxnm package as conflicting with network-manager-gnome I commented it at the LXDE mailing list, and they didn't like it at all as well I hope this situation can be fixed soon - and helping people who want to use LXDE working with nm-applet (network-manager-gnome package), or having the freedom of choice - even from a larger wireless managers diversity (which may help us to know which ones are the very better) -- Another thing: i were having difficulties on booting the Jaunty live-cd on a Macbook 2,0 - got completelly blank after usplash boot - please try asap also... thanks! Paulo ------------------------------------- On 3/27/09, James Westby <james.wes...@ubuntu.com> wrote: > This morning python2.6 version 2.6.1-1ubuntu5 made it in to Jaunty after > being held for a few days for the freeze. Unfortunately this package > contained an ABI break that meant some python extensions no longer > worked, most notably pygtk. In other words if you installed this version > you would see some apps fail to start with a message "undefined symbol: > PyUnicodeUCS4_DecodeUTF8". Most importantly update-manager was affected, > making it harder to upgrade to a fixed version. > > https://bugs.launchpad.net/ubuntu/+source/python2.6/+bug/349467/ > > Access to the bad packages was blocked, which is why you might have > seen 403 errors if you attempted to upgrade this morning, and fixed > packages have been uploaded as version 2.6.1-1ubuntu5.1. > > To find out if you have the bad version of the package installed you > can run > > dpkg -l python2.6 | cat > > If the version is not 2.6.1-1ubuntu5 then you are unaffected, you should > just be sure that you don't install that version if it is still > accessible on your mirror. > > If you do have the bad version installed then you can upgrade using > apt-get. > > sudo apt-get update > sudo apt-get upgrade > > The fixed packages have only just been made available on the primary > mirror, so you may need to wait a few hours before they can become > available. > > Thanks, > > James > > > -- > ubuntu-devel-announce mailing list > ubuntu-devel-annou...@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
