In Nautilus, when browsing in Icon View, it is currently impossible to distinguish between document types that provide previews without looking at their file extensions.

For example, if I have 2 similar documents side by side, one is a PDF, the other is an OpenOffice Writer document, they both look identical and I cannot tell which is the PDF without looking at the file extension.

See here for an example in Ubuntu 8.10:
http://www.flickr.com/photos/33359003@N00/3143087405/

Solution: Add a visual cue to the preview icon (either a mini file-type icon (like Windows), or simply a watermark with the file extension (like Mac OS X).

Windows and Mac examples:
http://www.jtbworld.com/images/PDFPreviewHandleralsowithAdobeReader8.1_16FD/ima ge.png
http://images.appleinsider.com/leopard-finder-071008-8.jpg

The ones with ~ at the end of them. This is not good for security and it's annoying.

There _is_ an option to disable this but, as it rightly points out, if it were to crash at any point in the saving process you've lost your edits.

I think this would be great for everybody, because OpenOffice 3.0 has A LOT of improvements that will help people that uses this kind of program constantly to migrate from MS Office to OpenOffice.
Support for MS Office 2007 documents and PDF editing are two good examples.

I know that Intrepid will be released in 15 days, but I think there aren't going to be a lot of crazy bugs to be fixed in "only" 15 days by developers if this program gets upgraded in Ubuntu repositories!

Think about that and let's do this now, instead of waiting more six months (Ubuntu 9.04) just to get this great program by default... you know, if more good programs comes by default, more the newbies and veterans will like!

By default there is Gimp image editor available in Ubuntu. This tool is "gorilla" like and is not so easy to use by beginners. This tool is for advanced users. We need some simple tool just like with editing there is Gedit (simple text editor) and there is OpenOffice Writer (gorilla software, powerful tool).

The current Kubuntu logo looks very nice. It looks very much like in the KDE 3 style.

When KDE 3 gets phased out, and Kubuntu uses KDE 4 (8.10?) I think we need a new Oxygen-style Kubuntu Logo!

We have wine for running Windows .exe's on linux, so why not a layer for running Mac .dmg's? Now that Apple has started using Intel chips, there is no problem with our x86 processors. There are plenty of apps out there developed for MacOSX that us linux users have no hope of running. While it might break the 'purity' of linux, it would not be installed by default and would do no more dirtying than wine.


(Note: I know that Wine Is Not an Emulator, but the official definition was too long for the title)

Stardock has released a desktop organizer tool that I found very useful, I think that doing something similar as a Compiz plugin would improve your desktop funcionality

reference:
http://www.stardock.com/products/fences/

I don't really like ideas that promote personal choices of application, but I think this is NOT the case this idea.

So why I think (K)MPlayer is the way to go?
It has on thing that makes it substantially better form the others it can be embedded in Firefox and in order to watch videos from internet (that are not flash; there are still few of other lurking around) you have to install it anyway.
So why it wouldn't be installed as default I don't like cluttering.
As of now I have 7! media or video players:
Kaffeine (default with KDE 3.5)
Helix (I installed it because I was used to Real Player)
KMPlayer
MPlayer (I don't know why I have both of them...)
Dragon (default KDE 4 player)
Xine (It's engine and a player??)
VLC (I wanted to watch IPTV on computer but never had time to actually make it work...)

Now if I issue dmesg command in terminal, i see something like this:
[ 3903.226359] dmesg report row

This is fine, just that I cannot figure out when happened the event. So, let's see the solution:

The i386 ISOs do not have anything to do with Intel or the 386 cpus specifically just as the amd64 are not specific to AMD processors. Additionally these descriptors are practically meaningless to non-techies.

What matters for the decision between the ISOs is the difference between 32bit and 64bit, not intel and amd, so why not just call them that way, and thus take away the burden of having to be a cpu technician to understand them?

EDIT: As a compromise, to avoid confusion of the x86/IA ISOs with those for other architectures, descriptors like PC32bit and PC64bit might also be acceptable as that is likely the maximum a home user knows about his or her computer.