First reason: all OS vendors / providers say the same about their newborn OSs. Why wouldn't he.
Then:
– this is the second release to have long term support (so it will have learnt a few lessons from the first release to offer this: Dapper Drake), 
- comes with KVM and VMware virtualization built in and comes in a stripped-down version called JEOS (Just Enough Operating System) for software "appliances" that run on virtual machines, does anyone remember VMware ESX ?
– better integration with Windows' Active Directory for corporate users
- a certified, downloadable version of Java software
- can be installed directly into the Windows file system so people can try it without having to reformat their hard drives. Pop in the disk and go play!
– better integration with web applications suck as flickr
- if you just cannot wait go to Ubuntu Hardy Heron Download and try the latest available beta.
– you'll also get the latest Firefox (3 beta 5), Brasero, Transmission, Vinagre, Totem and Inkscape

Enjoy!

Cheers…

via: www.news.com

This time I had a problem with my wireless connection.

If you can reproduce this then you have a problem too

1. Shut down your PC
2. Start it up and register onto a Wireless Network
3. Test that it actually works and you can load a webpage
4. Hibernate
5. Switch off your wireless router
6. Start up your PC
7. If you see the NetworkManager applet displaying the blue vertical bars and showing you that you are registered onto your wi-fi network then you have the same problem as I did.

This is how to solve it:
1. Open up sudo gedit /etc/default/acpi-support
2. Scroll down to STOP_SERVICES="" (you may actually have something in there but it does not matter)
3. Add networking to the list of services that are to be stopped and restarted when hibernating: you should now have something like STOP_SERVICES="networking"
4. Restart your PC
5. Try again the first steps to see if you still have the problem. If you do, post a message

Cheers…

I installed Gutsy Gibbon this Friday. Finally it worked like a charm. Even my resolution was set properly. I have a Dell Inspiron 6400 (aka e1505) and I have to say I did expect this
What I did not expect though was not being able to browse the internet on my wireless network.

Basically everything would simply resolve to 10.1.1.1 and my browser would just not work.

To cut long story short what I had to do was to first switch off  IPV6 in Firefox's (open new tab -> type about:config in the URL bar and hit Enter -> type IPV6 and then dbl click to set option to disable). Then I realized it was not enough My DNS servers were messed up.

Initially I put the correct DNS value (from my ISP) in  System -> Administrator -> Network -> DNS and though the internet worked the values were lost after a reboot.
Apparently the NetworkManager overwrites the /etc/resolv.conf. Oh well, there is not much one can do about that eh? When I was about to give up I discovered a file called: /etc/dhcp3/dhclient.conf
At the top of this file there is a line like this:
#prepend domain-name-servers 127.0.0.1;
All I had to do was to uncomment the line and replace the IP with my DNS. After I rebooted I checked the /etc/resolv.conf and my DNS was there.

I believe this problem is quite specific to some Wireless Routers / Modems. Mine is a D-Link and I suspect other people have the same problem as well.

I hope a future update will fix this problem.

Cheers…

Eventually you'd find out that by adding a line to your .bashrc all your problems are gone and when issuing an $ echo $JAVA_HOME everything would be okay.

The problem is though, that this setting is not picked up from X (graphical environment, e.g. Gnome) and when creating a launcher that needs this JAVA_HOME variable you'd find that the application won't start. I had this issue when creating a java launcher for IntelliJ Idea 7.0

Ubuntu comes to the rescue! In your /etc folder there is a environment file. Edit this file and add your JAVA_HOME variable, restart and ta da it magically works!
Here are the steps:

$ sudo gedit /etc/environment

In the editor not add the following line at the top:
JAVA_HOME="/usr/lib/jvm/java-1.5.0-sun"

Make sure that you replace java-1.5.0-sun with a valid location (this will work if you have jdk 5 installed).
Save and close! Reboot and let me know if it worked!

Cheers…

I say “used to” because thanks to some googling and some fiddling now I am finally able to resume my session after hibernating. Here is the whole story: I installed Ubuntu 7.04 Feisty Fawn and I made pretty much everything work:

• s-video out
• wireless
• widescreen display
• beryl
• bluetooth
• webcam

but after a while I decided to change my partitions. So I removed a former FAT32 partition and moved my SWAP around a little and then created a new ext3 partition to replace the FAT32 one. I included the new partition in the /etc/fstab and everything seemed to be fine. Until I realised that Hibernate stopped working. I would be able to Hibernate but on resume I would get a new log in screen instead of the lock screen password prompt.

I thought it was because I installed 915resolution, then I thought it was because I was running beryl or compwiz. Eventually I realized all my problems came from the fact that my swap partition was no longer available. Running

$ sudo free | grep Swap would return something like Swap: 2096472 0 2096472 which was a clear sign that my swap partition was not OK. Also

$ sudo swapon -a would return swapon: cannot stat /dev/disk/by-uuid/<SomeUUID>: No such file or directory

This was actually good for me because I knew right then what I needed to do: confirm that the UUID in the /etc/fstab did not match the one in the /etc/initramfs-tools/conf.d/resume
BINGO! They were different.

So here comes the solution:
1. find the swap partition
$ sudo fdisk -l | grep swap
/dev/sda5 1919 2049 1052226 82 Linux swap / Solaris

2. get sda5′s UUID
$ sudo vol_id /dev/sda5
ID_FS_USAGE=other
ID_FS_TYPE=swap
ID_FS_VERSION=2
ID_FS_UUID=09149dfb-7a3d-4276-a944-418a75d9490c
ID_FS_LABEL=
ID_FS_LABEL_SAFE=

3. update the /etc/fstab to use the 09149dfb-7a3d-4276-a944-418a75d9490c value instead of the one that was there for the swap partition
$ sudo gedit /etc/fstab

4. update the /etc/initramfs-tools/conf.d/resume and replace the existing uuid with the same value as above
$ sudo gedit /etc/fstab

5. update the initial ramdisk with the new uuid. If you want more info on initrd check out http://en.wikipedia.org/wiki/Initrd
$ sudo update-initramfs -u

6. Reboot (although probably it probably wasn’t necessary)

Now HIBERNATE works!

I hope this helps, if not feel free to post questions.

Cheers…

The end.

Cheers